Re: How do I restore data changes made after the backup?

We just encountered the same condition sited in the following post snipped
from Goggle groups:

>fredrik chabot <fredrik(at)f6(dot)nl> writes:
>> so I migrated the database to a non-smp machine running RH 7.2 and the
postgres
>> 7.2.1-5 rpm's<br>
>> <br>
>> Kernel 2.4.7-10<br>
>> <br>
>> and I still get
>> <blockquote type="cite" cite="mid25853(dot)1032724594(at)sss(dot)pgh(dot)pa(dot)us">
>> <pre wrap="">FATAL 1: LWLockAcquire: can't wait without a PROC
structure</pre>
>> </blockquote>
>> The code tells me this should never heppen :-&lt;<br>
>
>I don't think it should happen either ;-) When do you see it exactly
>--- is it during startup of a fresh connection, or while executing
>queries in an existing backend, or ...?
>
> regards, tom lane

I could not find any info that said the cause or cure had been identified.
Can anyone fill me in?

For the record:

ccc=# select version();
version
-------------------------------------------------------------
PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.96
(1 row)

Also a snip from our postmaster log:

2002-10-15 16:00:02 [2067] DEBUG: connection: host=10.1.2.100
user=BSPEIRS database=template1
2002-10-15 16:00:03 [2085] DEBUG: connection: host=10.1.2.100
user=BSPEIRS database=ccc
2002-10-15 16:00:03 [2086] DEBUG: connection: host=10.1.2.100
user=BSPEIRS database=template0
2002-10-15 16:00:03 [2086] FATAL 1: Database "template0" is not
currently accepting connections
2002-10-15 16:00:04 [2087] DEBUG: connection: host=10.1.2.100
user=BSPEIRS database=template0
2002-10-15 16:00:04 [2087] FATAL 1: Database "template0" is not
currently accepting connections
2002-10-15 16:00:04 [2087] FATAL 1: LWLockAcquire: can't wait without a
PROC structure
2002-10-15 16:00:04 [23427] DEBUG: server process (pid 2087) exited with
exit code 1
2002-10-15 16:00:04 [23427] DEBUG: terminating any other active server
processes

.... followed by a slew of "Postmaster has informed me..." messages.

The process attempting to connect was pgAdminII v1.2.0 .

Postgres had been up for 15 straight days prior to encountering this and
this is the first occurrence in 3 months of otherwise trouble-free up-time.
Any help in responding to this would be appreciated and we're open to
helping further diagnose if the cause is still undetermined.

Thanks,

Marc Mitchell - Senior Application Architect
Enterprise Information Solutions, Inc.
Downers Grove, IL 60515
marcm(at)eisolution(dot)com