Re: panic on 7.3 - Mailing list pgsql-hackers

Rick Gigger wrote:
> Postgres version 7.3.4
> 
> ... a whole bunch of other files....
> -rw-------  1 postgres postgres 262144 Jan 18 22:42 027D
> -rw-------  1 postgres postgres 262144 Jan 19 07:38 027E
> -rw-------  1 postgres postgres 262144 Jan 19 08:25 027F
> -rw-------  1 postgres postgres 262144 Jan 19 09:07 0280
> -rw-------  1 postgres postgres 262144 Jan 19 09:59 0281
> -rw-------  1 postgres postgres 262144 Jan 19 11:07 0282
> -rw-------  1 postgres postgres 262144 Jan 19 12:22 0283
> -rw-------  1 postgres postgres 262144 Jan 19 13:29 0284
> -rw-------  1 postgres postgres 262144 Jan 19 14:26 0285
> -rw-------  1 postgres postgres 262144 Jan 19 15:58 0286
> -rw-------  1 postgres postgres 262144 Jan 19 19:55 0287
> -rw-------  1 postgres postgres 262144 Jan 19 23:47 0288
> -rw-------  1 postgres postgres 262144 Jan 20 02:35 0289
> -rw-------  1 postgres postgres 262144 Jan 20 04:21 028A
> -rw-------  1 postgres postgres 262144 Jan 20 06:16 028B
> -rw-------  1 postgres postgres 262144 Jan 20 07:20 028C
> -rw-------  1 postgres postgres 262144 Jan 20 08:22 028D
> -rw-------  1 postgres postgres 262144 Jan 20 09:24 028E
> -rw-------  1 postgres postgres 262144 Jan 20 10:24 028F
> -rw-------  1 postgres postgres 262144 Jan 20 11:04 0290
> -rw-------  1 postgres postgres 262144 Jan 20 11:50 0291
> -rw-------  1 postgres postgres 262144 Jan 20 13:27 0292
> -rw-------  1 postgres postgres 262144 Jan 20 14:24 0293
> -rw-------  1 postgres postgres 262144 Jan 20 14:53 0294
> -rw-------  1 postgres postgres 262144 Jan 20 17:10 0295
> 
> That is right now.  Right after it started up it went up to 0292.  
> There are a lot of files before the ones listed here right now  
> though.  Do you need to see their names?

I assume you are missing one of these fixes in 7.3.X current which were
done _after_ 7.3.4 was released:
    * Fix race condition in transaction log management      There was a narrow window in which an I/O operation could
be     initiated for the wrong page, leading to an Assert      failure or data corruption.
 
    * Repair incorrect order of operations in GetNewTransactionId()      This bug could result in failure under
out-of-disk-space     conditions, including inability to restart even after      disk space is freed.
 

---------------------------------------------------------------------------


> 
> 
> On Jan 20, 2006, at 3:58 PM, Tom Lane wrote:
> 
> > Rick Gigger <rick@alpinenetworking.com> writes:
> >> I got this message:
> >> 2006-01-20 11:50:51 PANIC:  creation of file /var/lib/pgsql/data/
> >> pg_clog/0292 failed: File exists
> >
> >> In 7.3.  It caused the server to restart.
> >
> >> Can anyone tell me what it means?
> >
> > 7.3.what?
> >
> > What file names exist in the pg_clog directory?
> >
> >             regards, tom lane
> >
> > ---------------------------(end of  
> > broadcast)---------------------------
> > TIP 1: if posting/reading through Usenet, please send an appropriate
> >        subscribe-nomail command to majordomo@postgresql.org so that  
> > your
> >        message can get through to the mailing list cleanly
> >
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
> 
>                http://archives.postgresql.org
> 

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073