[BUGS] Bug #860: [7.3.x] pg_config --configure not readily usable
jmm ([EMAIL PROTECTED]) reports a bug with a severity of 3 The lower the number the more severe it is. Short Description [7.3.x] pg_config --configure not readily usable Long Description The use of quotes in pg_config --configure makes it not longer usable as ./configure argument Example: jmma@alpha:~/postgres> ./configure `pg_config --configure` configure: warning: '--enable-locale': invalid host type configure: warning: '--with-CXX': invalid host type configure: error: can only configure for one host and one target at a time jmma@alpha:~/postgres> Sample Code No file was uploaded with this report ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[BUGS] small bug? "ERROR: exprType: Do not know how to get type for 711 node"
nothing show-stopping, but something I found by accident: test=# select version(); version - PostgreSQL 7.3.1 on i386-unknown-freebsd4.7, compiled by GCC 2.95.4 (1 row) test=# create table foo (bar int); CREATE TABLE test=# update foo set foo=1 where foo=1; ERROR: exprType: Do not know how to get type for 711 node Only occurs when the column name used in the WHERE clause is the same as the table name but does not exist in the table. I would have expected a message more like this: test=# update foo set foo=1 ; ERROR: Relation "foo" has no column "foo" Ian Barwick [EMAIL PROTECTED] ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] Bug #855: pg_dump crash on linux-xfs
"Ruslan V. Lopatin" <[EMAIL PROTECTED]> writes:
> Program received signal SIGSEGV, Segmentation fault.
> 0x402d3557 in strlen () from /lib/libc.so.6
> (gdb) bt
> #0 0x402d3557 in strlen () from /lib/libc.so.6
> #1 0x08056ddc in WriteStr (AH=0x806c808, c=0x6c627570 "")
> at pg_backup_archiver.c:1519
> #2 0x0805752a in WriteToc (AH=0x806c808) at
> pg_backup_archiver.c:1851
> #3 0x0805a2ce in _CloseArchive (AH=0x806c808) at
> pg_backup_custom.c:802
Ohh ... I see the problem. It is this misguided effort at avoiding
memory leaks:
if (commentDeps)
{
for (j = 0; (*commentDeps)[j] != NULL; j++)
free((void *) (*commentDeps)[j]);
free(commentDeps);
}
(about line 5447 of pg_dump.c; added in rev 1.268 of 2-Jul-02).
This is freeing the dependency data that the archive entry needs :-(
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] Bug #860: [7.3.x] pg_config --configure not readily usable
[EMAIL PROTECTED] writes: > The use of quotes in pg_config --configure makes it not longer > usable as ./configure argument Add an eval: eval ./configure `pg_config --configure` The change is necessary to handle configure arguments that contain spaces... regards, tom lane ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [BUGS] small bug? "ERROR: exprType: Do not know how to get type for 711 node"
Ian Barwick <[EMAIL PROTECTED]> writes: > test=# create table foo (bar int); > CREATE TABLE > test=# update foo set foo=1 where foo=1; > ERROR: exprType: Do not know how to get type for 711 node Hmm, that used to behave properly in 7.2: regression=# create table foo (bar int); CREATE regression=# update foo set foo=1 where foo=1; ERROR: Attribute 'foo' not found Looks like we rearranged the order of operations and error checks in a bad way. Will look into it. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [BUGS] small bug? "ERROR: exprType: Do not know how to get type for 711 node"
Ian Barwick <[EMAIL PROTECTED]> writes: > test=# create table foo (bar int); > CREATE TABLE > test=# update foo set foo=1 where foo=1; > ERROR: exprType: Do not know how to get type for 711 node Now it does regression=# update foo set foo=1 where foo=1; ERROR: Relation reference "foo" cannot be used in an expression Thanks for the report. regards, tom lane ---(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
