Re: [BUGS] Postgresql 7.2.3
Dear sir(s)/madam(s), I have upgraded to 7.2.3 as advised. However, I still get the following errors: DEBUG: recycled transaction log file 00DE FATAL 2: open of /var/lib/pgsql/data/pg_clog/0747 failed: No such file or directory DEBUG: server process (pid 22689) exited with exit code 2 DEBUG: terminating any other active server processes NOTICE: Message from PostgreSQL backend: The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory. I have rolled back the current transaction and am going to terminate your database system connection and exit. Please reconnect to the database system and repeat your query. DEBUG: database system was interrupted at 2002-10-29 15:03:03 MYT DEBUG: checkpoint record is at 0/DFEDA738 DEBUG: redo record is at 0/DFEC7624; undo record is at 0/0; shutdown FALSE DEBUG: next transaction id: 3664616; next oid: 24748 DEBUG: database system was not properly shut down; automatic recovery in progress DEBUG: redo starts at 0/DFEC7624 DEBUG: ReadRecord: record with zero length at 0/DFFA5E80 DEBUG: redo done at 0/DFFA5E5C FATAL 1: The database system is starting up FATAL 1: The database system is starting up FATAL 1: The database system is starting up FATAL 1: The database system is starting up FATAL 1: The database system is starting up FATAL 1: The database system is starting up DEBUG: database system is ready DEBUG: recycled transaction log file 00DF DEBUG: recycled transaction log file 00E0 It seems to me that the fix in 7.2.3 doesn't do the job well? Any help is greatly appreciated! -- Vincent Lim Software Engineer NESTAC Solution Sdn Bhd [EMAIL PROTECTED] | +(6012) 659-6609 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[BUGS] Bug #807: Sequence currupted on recovery after kill -9
Matt Thompson ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Sequence currupted on recovery after kill -9
Long Description
If you create a file with an implied sequence and do a couple of inserts, then do a
kill -9, when you start up again, the sequence will have a corrupted next_value field.
In the example, the value of last_value is 4 before the kill -9 and 34 when it comes
back up.
Sample Code
[root@hawk temp]# cat list.txt
[postgres@buzzard tf]$ cat ins2.sh
psql testdb -c "create table test (id serial,name text);"
psql testdb -c "insert into test (name) values ('name1')"
psql testdb -c "insert into test (name) values ('name2')"
psql testdb -c "insert into test (name) values ('name3')"
psql testdb -c "insert into test (name) values ('name4')"
psql testdb -c "select * from test"
psql testdb -c "select * from test_id_seq"
cat data/postmaster.pid
[postgres@buzzard tf]$
[postgres@buzzard tf]$ ins2.sh
NOTICE: CREATE TABLE will create implicit sequence 'test_id_seq' for SERIAL column
'test.id'
NOTICE: CREATE TABLE / UNIQUE will create implicit index 'test_id_key' for table
'test'
CREATE
INSERT 41140 1
INSERT 41141 1
INSERT 41142 1
INSERT 41143 1
id | name
+---
1 | name1
2 | name2
3 | name3
4 | name4
(4 rows)
sequence_name | last_value | increment_by | max_value | min_value |
cache_value | log_cnt | is_cycled | is_called
---++--+-+---+-+-+---+---
test_id_seq | 4 |1 | 9223372036854775807 | 1 |
1 | 30 | f | t
(1 row)
19177
/home/tf/data
5432001 3342354
[postgres@buzzard tf]$ kill -9 19177
[postgres@buzzard tf]$ pg_ctl -l logfile start
pg_ctl: Another postmaster may be running. Trying to start postmaster anyway.
postmaster successfully started
[postgres@buzzard tf]$ psql testdb -c "select * from test_id_seq"
sequence_name | last_value | increment_by | max_value | min_value |
cache_value | log_cnt | is_cycled | is_called
---++--+-+---+-+-+---+---
test_id_seq | 34 |1 | 9223372036854775807 | 1 |
1 | 0 | f | t
(1 row)
No file was uploaded with this report
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
Re: [BUGS] Bug #807: Sequence currupted on recovery after kill -9
[EMAIL PROTECTED] writes: > If you create a file with an implied sequence and do a couple of > inserts, then do a kill -9, when you start up again, the sequence > will have a corrupted next_value field. In the example, the value > of last_value is 4 before the kill -9 and 34 when it comes back up. What version of PostgreSQL is this? Cheers, Neil -- Neil Conway <[EMAIL PROTECTED]> || PGP Key ID: DB3C29FC ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [BUGS] Bug #807: Sequence currupted on recovery after kill -9
On Tuesday 29 October 2002 08:23, Neil Conway wrote: > [EMAIL PROTECTED] writes: > If you create a file with an implied sequence and do a couple of > inserts, then do a kill -9, when you start up again, the sequence > will have a corrupted next_value field. In the example, the value > of last_value is 4 before the kill -9 and 34 when it comes back up. I'm sure if you read the footers on Tom's email's it's pretty clearly stated 'do not kill -9 the postmaster'. So I'm not so sure that this is really a bug. -- Darcy Buskermolen Wavefire Technologies Corp. ph: 250.717.0200 fx: 250.763.1759 http://www.wavefire.com ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [BUGS] Bug #807: Sequence currupted on recovery after kill -9
On Tue, 29 Oct 2002 [EMAIL PROTECTED] wrote: > Matt Thompson ([EMAIL PROTECTED]) reports a bug with a severity of 2 > The lower the number the more severe it is. > > Short Description > Sequence currupted on recovery after kill -9 > > Long Description > If you create a file with an implied sequence and do a couple of inserts, then do a >kill -9, when you start up again, the sequence will have a corrupted next_value >field. In the example, the value of last_value is 4 before the kill -9 and 34 when >it comes back up. > The purpose of a sequence is not to insure that the numbers are consecutive, only to insure that they are unique. If you have failed inserts, you will see holes also. I don't know off the top of my head how to do consecutive numbers. Maybe only with a table lock. - robert ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [BUGS] Bug #807: Sequence currupted on recovery after kill -9
[EMAIL PROTECTED] writes: > Sequence currupted on recovery after kill -9 > Long Description > If you create a file with an implied sequence and do a couple of inserts, then do a >kill -9, when you start up again, the sequence will have a corrupted next_value >field. In the example, the value of last_value is 4 before the kill -9 and 34 when >it comes back up. This is not corruption, it is the intended behavior. Only if the sequence were to go backwards would we consider it a bug. (There were some sequence-can-go-backwards bugs awhile ago ... but since you didn't say what version you are using, it's impossible to guess whether you need an upgrade.) regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] Bug #807: Sequence currupted on recovery after kill -9
Robert Hentosh wrote: > On Tue, 29 Oct 2002 [EMAIL PROTECTED] wrote: > > > Matt Thompson ([EMAIL PROTECTED]) reports a bug with a severity of 2 > > The lower the number the more severe it is. > > > > Short Description > > Sequence currupted on recovery after kill -9 > > > > Long Description > > If you create a file with an implied sequence and do a couple of inserts, then do >a kill -9, when you start up again, the sequence will have a corrupted next_value >field. In the example, the value of last_value is 4 before the kill -9 and 34 when >it comes back up. > > > > > The purpose of a sequence is not to insure that the numbers are > consecutive, only to insure that they are unique. If you have failed > inserts, you will see holes also. > > I don't know off the top of my head how to do consecutive numbers. Maybe > only with a table lock. Right. Sequences aren't consecutive anyway because an ABORT will not reuse the sequence value. There is an FAQ on that. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [BUGS] Bug #797: Inaccurate in PostgreSQL 7.3b2 Developer's Guide
Patch attached. SGML docs updated. Thanks. --- [EMAIL PROTECTED] wrote: > Piotr Kuczynski ([EMAIL PROTECTED]) reports a bug with a severity of 4 > The lower the number the more severe it is. > > Short Description > Inaccurate in PostgreSQL 7.3b2 Developer's Guide > > Long Description > There is small inaccurate in the "PostgreSQL 7.3b2 Developer's Guide": > > [Chapter 10. Native Language Support] > [10.1.3. Creating and maintaining message catalogs] > [paragraph 5th] > "(...) This will create a file progname.pot. (.pot to distinguish it from PO files >that are "in production". What does the T stand for? I don't know.) (...)" > > > In the documentation of Translation Project >(http://www.iro.umontreal.ca/contrib/po/HTML/), chapter "Software to use", you can >read: > "(...) these older versions produce PO files or PO Template files (...)" > > If I understood well the T after PO stands for Tamplate, right? So, the "PostgreSQL >7.3b2 Developer's Guide" frgament I cited above should look like: > "(...) This will create a file progname.pot. (.pot to distinguish it from PO files >that are "in production". The T stands for Template.) (...)" > > Regards > > Piotr Kuczynski > Hypode > > Sample Code > > > No file was uploaded with this report > > > ---(end of broadcast)--- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to [EMAIL PROTECTED] so that your > message can get through to the mailing list cleanly > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 Index: doc/src/sgml/nls.sgml === RCS file: /cvsroot/pgsql-server/doc/src/sgml/nls.sgml,v retrieving revision 1.4 diff -c -c -r1.4 nls.sgml *** doc/src/sgml/nls.sgml 22 Mar 2002 19:20:15 - 1.4 --- doc/src/sgml/nls.sgml 30 Oct 2002 05:13:17 - *** *** 176,183 This will create a file progname.pot. (.pot to distinguish it from PO files that ! are in production. What does the T stand for? I ! don't know.) Copy this file to language.po and edit it. To make it known that the new language is available, also edit the file nls.mk and add the --- 176,184 This will create a file progname.pot. (.pot to distinguish it from PO files that ! are in production. The T stands for ! template.) ! Copy this file to language.po and edit it. To make it known that the new language is available, also edit the file nls.mk and add the ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
