Архив рассылок [pgsql-bugs]
Re: BUG #8013: Memory leak Rae Stiening
BUG #8026: pgAdmin III FATAL: Cannot open the logfile! jevgeni.virves@gmail.com
BUG #8024: Let OS-XP display dead blue screen while run PG_DUMP yychen@mail.clhs.tyc.edu.tw
BUG #8027: Get generated key value while inserting in partitioned
table mohansammeta@gmail.com
BUG #8036: how to disable toasting zahid.quadri@cloverinfotech.com
Re: BUG #8036: how to disable toasting Bruce Momjian
Re: BUG #8036: how to disable toasting Kevin Grittner
pg_stat_statements doesn't work with --disable-spinlocks Heikki Linnakangas
Installation crashes HGuardia
BUG #8043: 9.2.4 doesn't open WAL files from archive,
only looks in pg_xlog bohmer@visionlink.org
Re: John R Pierce
Re: 9.2.4: Strange behavior when wildcard is on left side of
search string Christopher Browne
BUG #8046: PL/pgSQL plan caching regression dmitigr@gmail.com
Re: BUG #8046: PL/pgSQL plan caching regression Dmitriy Igrishin
Re: [HACKERS] Re: BUG #8043: 9.2.4 doesn't open WAL files
from archive, only looks in pg_xlog Christoph Berg
BUG #8048: Text Search luigisag@gmail.com
Re: BUG #8048: Text Search Kevin Grittner
Re: BUG #8048: Text Search Tom Lane
BUG #8050: Need quotes around service exe (imagepath registry key) mr_gapearce@yahoo.com
replication_timeout not effective Dang Minh Huong
Re: replication_timeout not effective Amit Kapila
BUG #8056: postgres forgets hstore over time knowzerox@yahoo.com
Fwd: replication_timeout not effective Dang Minh Huong
Re: replication_timeout not effective Amit Kapila
Re: replication_timeout not effective Dang Minh Huong
Re: BUG #8056: postgres forgets hstore over time Dickson S. Guedes
Re: replication_timeout not effective Kyotaro HORIGUCHI
Re: replication_timeout not effective Andres Freund
Re: replication_timeout not effective Dang Minh Huong
Re: replication_timeout not effective Andres Freund
Re: replication_timeout not effective Dang Minh Huong
Re: BUG #8056: postgres forgets hstore over time John R Pierce
BUG #8058: CLUSTER and VACUUM FULL fail to free space daniel@heroku.com
BUG #8059: sequence crash recovery is not working properly tarvip@gmail.com
BUG #8060: postgresql service not in Microsoft services shaun.c.mccrery@saic.com
postgres 8.4 PQexec hang on HP-UX Singh, Devendra
BUG #8057: Unable to Connect PostgresSQL Remotely rajuk058@gmail.com
Re: BUG #8057: Unable to Connect PostgresSQL Remotely Dickson S. Guedes
BUG #8061: Not count limit offset claudiomsi@hotmail.com
Re: BUG #8061: Not count limit offset Dickson S. Guedes
Re: BUG #8059: sequence crash recovery is not working properly Tarvi Pillessaar
Re: postgres 8.4 PQexec hang on HP-UX Heikki Linnakangas
Re: postgres 8.4 PQexec hang on HP-UX Singh, Devendra
BUG #8067: now() bug? kako@zhnet.hu
Re: BUG #8067: now() bug? Tom Lane
general question and BUG #5038 Sofer, Yuval
Re: wrong search_path being used Erika31
BUG #8079: pg_ctl is killed by windows service controller due to
"Timed out waiting for server startup" event krzbia@interia.pl
BUG #8080: 32-bit ODBC Driver Needs timestamp MetaData Type victor@maintstar.com
Re: general question and BUG #5038 Jeff Davis
BUG #8091: No permissions on the table file causing recovery failure haribabu.kommi@huawei.com
BUG #8092: pg_dump need sur quoting schema name xavier.mouton-dubosc@notalus.fr
Re: BUG #8092: pg_dump need sur quoting schema name Alvaro Herrera
BUG #8094: psql prompt variable and command substitution broken nyetter@gmail.com
Re: BUG #8092: pg_dump need sur quoting schema name Xavier Mouton-Dubosc
BUG #8093: After starting postgres,
any attempt to connect generate a core dump and unable to login bmohareb@gmail.com
BUG #8095: postgres acquiring lock on a table when not in transaction vaiayand@gmail.com
BUG #8096: unable to create language PLl/TCL visionsw@sltnet.lk
BUG #8097: pg_dump incomplete data output wouter.boasson@rivm.nl
BUG #8098: Bad option -I in contrib/start-scripts/linux catherine.devlin@gmail.com
missing attachment for bug 8095 Nachiket Vaidya
BUG #8106: Redundant function definition in contrib/cube/cube.c ams214@cam.ac.uk
Re: BUG #8106: Redundant function definition in contrib/cube/cube.c Heikki Linnakangas
Fw: [pgadmin-support] (Bug) Numeric fault calculation Kanitchet Vaiassava
BUG #8107: How to downgrade database from 9.2.3 to 8.4 ? roberto.menoncin@netspa.it
Re: Fw: [pgadmin-support] (Bug) Numeric fault calculation Kevin Grittner
BUG #8113: odbc umberto.brighetti@gmail.com
Re: BUG #8091: No permissions on the table file causing recovery
failure Heikki Linnakangas
BUG #8114: Peer authentication in cgi-perl support@securenetterm.com
Re: BUG #8114: Peer authentication in cgi-perl John R Pierce
BUG #8115: Increased session memory usage after pg_upgrade danielcristian@gmail.com
BUG #8116: create trigger after insert fails if procedure being
executed is having error nitinmn@gmail.com
BUG #8117: simple but huge query infinite execution time haddock@mail.ru
Re: BUG #8114: Peer authentication in cgi-perl John R Pierce
Re: BUG #8118: Wrong sorting text Daniele Varrazzo
BUG #8124: How to uninstall and reinstall postgreSQL 9.2 eleasar22@gmail.com
Re: BUG #8124: How to uninstall and reinstall postgreSQL 9.2 Sandeep Thakkar
Optimizer problem with multi-column index Marc Schablewski
BUG #8125: server connecting error pradip29@gmail.com
BUG #8127: After failed insert a select to figure out what failed is
rejected matti.aarnio@methics.fi
Re: BUG #8118: Wrong sorting text whiplash
BUG #8126: error in translation dutch dennis.coomans@hva.nl
Re: BUG #8125: server connecting error deepuyadagiri
Re: BUG #8125: server connecting error John R Pierce
RESET ROLE issue (Unreproduceable (so far) ) Josh Berkus
Fw: [pgadmin-support] (Bug) Numeric fault calculation Kanitchet Vaiassava
ISSUE after upgrading to POSTGRES 8.4.8 Bansal, Pradeep
Re: ISSUE after upgrading to POSTGRES 8.4.8 Heikki Linnakangas
Re: ISSUE after upgrading to POSTGRES 8.4.8 John R Pierce
Re: ISSUE after upgrading to POSTGRES 8.4.8 Bansal, Pradeep
BUG #8128: pg_dump (>= 9.1) failed while dumping a scheme named "old"
from PostgreSQL 8.4 Adrian.Vondendriesch@credativ.de
Re: BUG #8128: pg_dump (>= 9.1) failed while dumping a scheme
named "old" from PostgreSQL 8.4 Adrian Vondendriesch
Re: ISSUE after upgrading to POSTGRES 8.4.8 John R Pierce
