Tom,
> Good. I am dead tired and am about to go to bed, but if you can
> reproduce with a debuggable build then I would definitely like to
> crawl into it tomorrow.
Good night. We can pick this up tomorrow.
> At this point I do not have the faintest idea what might cause the
> problem to go away, so if possible I'd urge you to do the minimum
> possible work on the system overnight. Alternatively, if you can
> spare the disk space, make a tarball copy of the whole $PGDATA
> tree while you have the postmaster shut down. Then we can
> study the problem offline without worrying about your live
> application.
I need the app up and running, but I did shut it down and created a backup of the entire directory as you suggested.
thanks,
--Barry
Tom Lane wrote:
>Barry Lind <barry@xythos.com> writes:
>
>
>>No. Restarting the postmaster does not resolve the problem.
>>
>>
>
>Now you've got my attention ;-) ... this is completely at variance
>with my theories about the cause of the problem. Destruction of
>a theory is usually a sign of impending advance.
>
>
>
>>I am going
>>to put the debug build in place and see if I can still reproduce.
>>
>>
>
>Good. I am dead tired and am about to go to bed, but if you can
>reproduce with a debuggable build then I would definitely like to
>crawl into it tomorrow.
>
>At this point I do not have the faintest idea what might cause the
>problem to go away, so if possible I'd urge you to do the minimum
>possible work on the system overnight. Alternatively, if you can
>spare the disk space, make a tarball copy of the whole $PGDATA
>tree while you have the postmaster shut down. Then we can
>study the problem offline without worrying about your live
>application.
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
>http://archives.postgresql.org
>
>
>
