Re: [BUGS] BUG #3852: Could not create complex aggregate

2008-01-07 Thread Tom Lane
Joe Conway <[EMAIL PROTECTED]> writes: > Did you want me to work on this? I could probably put some time into it > this coming weekend. I'll try to get to it before that --- if no serious bugs come up this week, core is thinking of wrapping 8.3.0 at the end of the week, so it'd be nice to have th

Re: [BUGS] ALTER INDEX/ALTER TABLE on indexes can cause unrestorable dumps

2008-01-07 Thread Alvaro Herrera
dup 3854 thanks Stefan Kaltenbrunner wrote: > the reason for this seems to be that pg_dump is using the constraint name > (which is not changed by ALTER TABLE/ALTER INDEX) and not the index name to > dump this kind of information but I wonder if it would actually be more > sensible (until we g

[BUGS] ALTER INDEX/ALTER TABLE on indexes can cause unrestorable dumps

2008-01-07 Thread Stefan Kaltenbrunner
Andy just reported on IRC that renaming indexes can lead to unrestorable dumps under certain circumstances. A simple example(8.2 but at least 8.1 and 8.3 seem to behave exactly the same) for that is: test=# CREATE TABLE foo(bar int PRIMARY KEY); NOTICE: CREATE TABLE / PRIMARY KEY will create i

[BUGS] BUG #3854: pg_dump dumps renamed primary key constraints by their old name

2008-01-07 Thread Milen A. Radev
The following bug has been logged online: Bug reference: 3854 Logged by: Milen A. Radev Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.6 Operating system: Debian Etch Description:pg_dump dumps renamed primary key constraints by their old name Details: Afte

Re: [BUGS] BUG #3808: Connections stays open in stateCLOSE_WAIT

2008-01-07 Thread Daniel Migowski
Tom Lane schrieb: "Dave Page" <[EMAIL PROTECTED]> writes: From: Bruce Momjian <[EMAIL PROTECTED]> Should we require the form to tell us their exact version number and throw an error if it isn't the current one? Past experience with other bug systems tells me we'll just end up wit

Re: [BUGS] BUG #3850: Incompatibility among pg_dump / pg_restore.

2008-01-07 Thread Stefan Kaltenbrunner
Diego Spano wrote: Stefan / List, these are the steps: 1- pg_dump sicoba|gzip>/home/backups/pg_backup/backup.pg 2- createdb sicoba6 3- psql -d sicoba6 < backup.pg And thats all. Errors appear when trying to add rows to first table, and so on... Find attached backup.pg. ok just took a l

Re: [BUGS] BUG #3852: Could not create complex aggregate

2008-01-07 Thread Joe Conway
Tom Lane wrote: "Sokolov Yura" <[EMAIL PROTECTED]> writes: create or replace function add_group(grp anyarray, ad anyelement, size int4) returns anyarray language plpgsql ... create aggregate build_group(anyelement, int4) ( SFUNC= add_group, STYPE = anyarray ); ERROR: argument declared

Re: [BUGS] BUG #3853: Autovacuum not working

2008-01-07 Thread Bill Moran
In response to "Christopher Brian L. Jurado" <[EMAIL PROTECTED]>: > > The following bug has been logged online: > > Bug reference: 3853 > Logged by: Christopher Brian L. Jurado > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.1.2 > Operating system: Windows XP/2003

[BUGS] BUG #3853: Autovacuum not working

2008-01-07 Thread Christopher Brian L. Jurado
The following bug has been logged online: Bug reference: 3853 Logged by: Christopher Brian L. Jurado Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.2 Operating system: Windows XP/2003 Description:Autovacuum not working Details: I can see in the server logs