[BUGS] BUG #1672: Postgres 8.0 doesn't return errors.
The following bug has been logged online: Bug reference: 1672 Logged by: Gregory L Miller-Kramer Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.2 Operating system: CentOS 4.0 Description:Postgres 8.0 doesn't return errors. Details: To Whom it may concern: Postgres8 does not return errors for some reason. If you look at the errors generated on dev or purposely cause an error in psql you will see what I mean. All errors are being dumped to /opt/pgsql/pgstartup.log. I'm thinking maybe this is a config option when postgres is built? Or maybe a bug in Postgres8? I had originally thought this was fixed by removing the $PGLOG from the the postgres startup script and restarting postgres. However, all that did was dump errors to STDOUT rather than the log file, so it looked to me like the problem was fixed. However, after I logged out of pgsql, I saw that I was still getting errors on the console from other people and the apps, etc. And when I closed my shell, all errors were lost, so I had to put the change back so that we could at least find the errors in pgstartup.log if we need them. When we used 7.4.2 we did not have this issue. The errors would disply in psql as well as in the web page. We are using Apache, mod_perl, and apache::ASP... Thank you, Greg Miller-Kramer ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [BUGS] BUG #1670: pg_dump fails on CentOS 4
Tom, Try turning off SELinux enforcement, or better update the selinux policy package and do a restorecon on all of /usr/bin. The earlier I'll definitely give this a try. Does this policy also apply to binaries compiled on the local machine? When I compiled PG803 from source, then copied pg_dump to /usr/bin as root, pg_dump worked fine. Thanks for the help! --Josh ---(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 #1672: Postgres 8.0 doesn't return errors.
On Mon, May 16, 2005 at 02:16:34PM +0100, Gregory L Miller-Kramer wrote: Postgres8 does not return errors for some reason. In what context? If you look at the errors generated on dev or purposely cause an error in psql you will see what I mean. Please provide an example so we can see exactly what you're talking about; the bug report doesn't contain enough information to duplicate the problem. What's the output of SHOW client_min_messages;? -- Michael Fuhr http://www.fuhr.org/~mfuhr/ ---(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] pg_restore: internal data corruption?
From manual examination of the code, it looks like pg_restore will corrupt an internal data structure on certain abnormal inputs. File: postgresql-8.0.2/src/bin/pg_dummp/pg_backup_archiver.c SortTocFromFile pulls dump IDs out of a file and uses them to sort the list entries in field toc of archive handle AH. If the same ID appears twice in a row in the file (which seems reasonable, since the file is human-readable and a fair amount of input validation is already performed on it), it looks like this list will be corrupted: tePrev is initialized to the head of the list (L886). With each iteration of the inner loop, the entire list (including the sorted portion) is scanned for the entry with the ID just pulled off the file (L917). If the specified entry is found, it is moved to the position immediately after tePrev (L924), and tePrev is advanced (L925). Since tePrev is in the scanned portion of the list, it should be returned by getTocEntryByDumpId if the same ID is provided twice in a row. _moveAfter will then be called with aliased pointers, corrupting the list: the referenced value will have two self cycles, and will be skipped over by the next pointers but not the prev. Thanks for looking at this, Brian Hackett ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] pg_restore: internal data corruption?
Brian Hackett [EMAIL PROTECTED] writes: From manual examination of the code, it looks like pg_restore will corrupt an internal data structure on certain abnormal inputs. Yeah, I think you are right. Looks easy to fix though: we already are building a flag array from the input, so just add a test to ignore any already-seen ID. Thanks for the report. regards, tom lane ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [BUGS] BUG #1661: JDBC DatabaseMetaData.getExportedKeys() returns
On Wed, 11 May 2005, Pavel Krupets wrote: Bug reference: 1661 PostgreSQL version: 8.0.2 Description:JDBC DatabaseMetaData.getExportedKeys() returns invalid keys. If I ask getExportedKeys(null, bc4jgen_test_04, table_03) to return exported foreign keys it will return 'fk_table_05_2_table_03' key. But this key isn't exported. table_05 does not references table_03's primary key, just a unique one! Please check javadocs excerpts below. I guess we consider this a feature, not a bug. Otherwise there is no way to retrieve foreign key information for foreign keys to unique constraints. If you've got a concrete reason why this is a bad thing please let us know. The javadoc does indeed say primary key, but I don't see why including unique ones as well is a problem. Kris Jurka ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] BUG #1672: Postgres 8.0 doesn't return errors.
Gregory L Miller-Kramer [EMAIL PROTECTED] writes: Postgres8 does not return errors for some reason. If you look at the errors generated on dev or purposely cause an error in psql you will see what I mean. All errors are being dumped to /opt/pgsql/pgstartup.log. This report is pretty unclear, but are you complaining that there's nothing in pgstartup.log? There's not supposed to be; that file only exists to catch any error messages that might come out before the error logging mechanism is started up. The default logging arrangement in the 8.0 RPMs is that postmaster log output goes into day-named log files under /var/lib/pgsql/data/pg_log/. If you don't like that, feel free to adjust the postgresql.conf parameters that control it. regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] BUG #1672: Postgres 8.0 doesn't return errors.
On Tue, May 17, 2005 at 05:05:03PM -0400, Gregory L Miller-Kramer wrote: On system One I enter the database ... psql exdb exdb select misspelled_excol from extable; and an error is displayed... ERROR: column 'misspelled_excol' does not exist On the Other system (Postgres 8.0) that error is NOT displayed. Infact, nothing is displayed it just returns to the prompt. As I asked in my previous message, what's the output of the following query? SHOW client_min_messages; My first guess is that client_min_messages is set to fatal or panic, which, although not among the documented settings for client_min_messages, are allowed and would have the effect you describe: test= SET client_min_messages TO panic; SET test= SELECT misspelled_excol FROM extable; test= SET client_min_messages TO notice; SET test= SELECT misspelled_excol FROM extable; ERROR: column misspelled_excol does not exist -- Michael Fuhr http://www.fuhr.org/~mfuhr/ ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [BUGS] BUG #1671: Long interval string representation rejected
Mark Dilger wrote: It appears that any string representation of an interval of length greater than 76 is rejected. (76 = 51 + 25 = MAXDATELEN + MAXDATEFIELDS). This appears to be a limitation enforced within function interval_in() in the file src/backend/utils/adt/timestamp.c Yeah, this seems bogus. It's not even clear to me why MAXDATELEN + MAXDATEFIELDS is used as the size of that buffer in the first place. I don't know the datetime code particularly well; perhaps someone who does can shed some light on this? -Neil ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
