• Text Size: Normal / Large
• Donate
• Contact

Section Navigation

• Community
• Contributors
• Mailing Lists
  • Subscribe
  • User lists
    • pgsql-admin
    • pgsql-advocacy
    • pgsql-announce
    • pgsql-bugs
    • pgsql-docs
    • pgsql-cygwin
    • pgsql-general
    • pgsql-interfaces
    • pgsql-jdbc
    • pgsql-jobs
    • pgsql-novice
    • pgsql-odbc
    • pgsql -performance
    • pgsql-php
    • pgsql-ports
    • pgsql-sql
  • Developer lists
  • Regional lists
  • Project lists
  • User groups
  • Inactive lists
• IRC
• Featured Users
• International Sites
• Propaganda
• Resources
• Weekly News
• Community login
  • Profile
  • Lost password

pgsql-bugs 2008-04 Chronological Index (1/2)

• Thread Index
• [Prev Page]
• [Next Page]

• 29 April 2008
  • BUG #4133: Installation error Anthony
  • Re: BUG #4132: REASSIGN OWNED fails on procedural languages Alvaro Herrera
  • Re: BUG #4132: REASSIGN OWNED fails on procedural languages Alvaro Herrera
  • BUG #4132: REASSIGN OWNED fails on procedural languages Kirill Simonov
  • Re: postmaster segfault when using SELECT on a table Karsten Desler
• 28 April 2008
  • Re: PB with postgresql 7.4 Sam Mason
  • PB with postgresql 7.4 Nicolas ZABOURI
  • Re: postmaster segfault when using SELECT on a table Zdenek Kotala
  • Re: postmaster segfault when using SELECT on a table Zdenek Kotala
  • Re: BUG #3833: Index remains when table is dropped Mark Kirkwood
  • Re: BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver valgog
• 26 April 2008
  • Re: postmaster segfault when using SELECT on a table Tom Lane
  • Re: postmaster segfault when using SELECT on a table Karsten Desler
  • Re: postmaster segfault when using SELECT on a table Tom Lane
  • postmaster segfault when using SELECT on a table Karsten Desler
• 25 April 2008
  • Re: BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver Kevin Grittner
  • Re: BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver valgog
  • Re: problem Zdenek Kotala
• 24 April 2008
  • Re: BUG #4128: The postmaster.opts.default file is begin ignored Tom Lane
  • Re: BUG #4128: The postmaster.opts.default file is begin ignored Peter Eisentraut
  • Re: BUG #4128: The postmaster.opts.default file is begin ignored Alvaro Herrera
  • Re: BUG #4128: The postmaster.opts.default file is begin ignored Tom Lane
  • Re: BUG #4126: KRB5/GSSAPI authenication fails for multipart kerberos principals Peter Koczan
  • BUG #4128: The postmaster.opts.default file is begin ignored Gary Jay Peters
  • Re: BUG #4127: pg_dumpall -c unable to be restored without error Jacob Champlin
  • Re: BUG #4127: pg_dumpall -c unable to be restored without error Tom Lane
  • BUG #4127: pg_dumpall -c unable to be restored without error Jacob Champlin
  • Re: HELP pls spol(at)mail(dot)ru
  • Re: Re: BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver Kris Jurka
• 23 April 2008
  • BUG #4126: KRB5/GSSAPI authenication fails for multipart kerberos principals Peter Koczan
  • Re: HELP pls Tom Lane
  • Re: HELP pls Alvaro Herrera
  • Re: BUG #4125: Strange ALTER TABLE behavior Vladimir Kanazir
  • Re: BUG #4125: Strange ALTER TABLE behavior Tom Lane
  • BUG #4125: Strange ALTER TABLE behavior Vladimir Kanazir
  • Re: Harald Armin Massa
  • Re: Bill Moran
  • [no subject] Adiel Davids
  • Re: BUG #4124: Error message: "You local administrators group contains 'Service users' this is a common configurat Gregory Stark
  • Re: BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver valgog
  • Re: BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver valgog
  • Re: Patch for LISTEN/NOTIFY race condition? Meetesh Karia
  • BUG #4124: Error message: "You local administrators group contains 'Service users' this is a common configurat Blake Lovely
• 22 April 2008
  • problem Khobotko Oleg
  • HELP pls spol(at)mail(dot)ru
  • help me please spol(at)mail(dot)ru
  • Re: Patch for LISTEN/NOTIFY race condition? Tom Lane
  • Re: Patch for LISTEN/NOTIFY race condition? Alvaro Herrera
  • Re: BUG #4122: ./postres 'restart' does not start server with same options as 'start' does Gary Doades
  • Patch for LISTEN/NOTIFY race condition? Meetesh Karia
  • Re: BUG #4122: ./postres 'restart' does not start server with same options as 'start' does Stefan Kaltenbrunner
  • Re: BUG #4122: ./postres 'restart' does not start server with same options as 'start' does Eugen.Konkov
  • Re: DISTINCT MAX() results mismatch on 8.2 and 8.3 Tom Lane
  • Re: BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver Kris Jurka
  • Re: DISTINCT MAX() results mismatch on 8.2 and 8.3 Kevin Grittner
  • Re: BUG #4122: ./postres 'restart' does not start server with same options as 'start' does Tom Lane
  • Re: ERROR: failed to re-find parent key in "sl_seqlog_idx" for deletion target John Parnefjord
  • Re: ERROR: failed to re-find parent key in "sl_seqlog_idx" for deletion target Magnus Hagander
  • Re: ERROR: failed to re-find parent key in "sl_seqlog_idx" for deletion target John Parnefjord
  • BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver Amit Mujawar
  • BUG #4122: ./postres 'restart' does not start server with same options as 'start' does Eugen Konkov
  • Re: ERROR: failed to re-find parent key in "sl_seqlog_idx" for deletion target Magnus Hagander
  • Re: BUG #4121: ERROR: could not open relation 1663/16403/469917: Invalid argument Zdenek Kotala
  • ERROR: failed to re-find parent key in "sl_seqlog_idx" for deletion target John Parnefjord
  • BUG #4121: ERROR: could not open relation 1663/16403/469917: Invalid argument Boldinov
• 21 April 2008
  • Re: BUG #4113: server closed the connection unexpectedly Tom Lane
  • Re: BUG #4120: ERROR: cache lookup failed for function 0 Tom Lane
  • Re: BUG #4120: ERROR: cache lookup failed for function 0 Pedro Gimeno
  • Re: BUG #4113: server closed the connection unexpectedly Tom Lane
  • Re: BUG #4113: server closed the connection unexpectedly Alvaro Herrera
  • Re: BUG #4113: server closed the connection unexpectedly Bruce Momjian
  • Re: BUG #4120: ERROR: cache lookup failed for function 0 Tom Lane
  • Re: pg_dump error when dumping mixed-case name tables Tom Lane
  • BUG #4120: ERROR: cache lookup failed for function 0 Pedro Gimeno
  • Re: 'Too many LWLocks held' with GIN pg_trgm_ops index [RE-SENT] Teodor Sigaev
  • pg_dump error when dumping mixed-case name tables Prischepa Vladimir
  • 'Too many LWLocks held' with GIN pg_trgm_ops index [RE-SENT] Craig Ringer
  • BUG #4119: Add foreign key fails for non-presence of a record that does exist. Buk
• 20 April 2008
  • Re: BUG #4114: Inconsistent shift operator Sam Mason
  • Re: Inconsistent shift operator Sam Mason
  • Re: BUG #4114: Inconsistent shift operator Zdenek Kotala
  • Re: Inconsistent shift operator Peter Eisentraut
  • Re: Inconsistent shift operator Tom Lane
  • Re: BUG #4115: PostgreSQL ISO format is not really ISO Peter Eisentraut
  • Re: Inconsistent shift operator Sam Mason
• 19 April 2008
  • Re: BUG #4115: PostgreSQL ISO format is not really ISO Daniel Ruoso
  • Re: BUG #4115: PostgreSQL ISO format is not really ISO Jaime Casanova
  • Re: Inconsistent shift operator Tom Lane
  • BUG #4116: Cannot create tablespace: could not set permissions on directory Graham Leggett
  • BUG #4115: PostgreSQL ISO format is not really ISO Daniel Ruoso
  • BUG #4114: Inconsistent shift operator Roman Kononov
  • Inconsistent shift operator Roman Kononov
• 18 April 2008
  • BUG #4113: server closed the connection unexpectedly Javier Hernandez
  • Re: Request Terry Lee Tucker
  • Request Adhikari, Tika Ram
• 17 April 2008
  • BUG #4112: Error on access table's data Malcus
  • Re: Server does not start when log_statement_stats is set to on Alvaro Herrera
  • Re: BUG: Protocol 3.0 ErrorResponse: Last 'null' characterseems odd Eugen.Konkov
  • BUG #4110: Error on select doing (date +1) Josep Llort
  • Re: BUG #4109: Typo in documentation Fujii Masao
• 16 April 2008
  • Re: BUG: Protocol 3.0: that's just odd, needing to add the number of bytes the length field occupies Bruce Momjian
  • Re: BUG: Protocol 3.0: that's just odd, needing to add the number of bytes the length field occupies Tom Lane
  • Re: BUG: Protocol 3.0 ErrorResponse: Last 'null' characterseems odd Tom Lane
  • Re: BUG #4109: Typo in documentation Heikki Linnakangas
  • Re: BUG: Protocol 3.0 ErrorResponse: Last 'null' characterseems odd Eugen.Konkov
  • Re: BUG: Protocol 3.0 ErrorResponse: Last 'null' character seems odd Alvaro Herrera
  • BUG: Protocol 3.0 ErrorResponse: Last 'null' character seems odd Eugen.Konkov
  • BUG #4109: Typo in documentation Fujii Masao
  • BUG: Protocol 3.0: that's just odd, needing to add the number of bytes the length field occupies Eugen.Konkov
• 15 April 2008
  • domains missing some default castings Pavel Stehule
  • BUG #4108: PgInstaller Update modify install paths in Registry Gildas PRIME
  • Re: BUG #3983: pgxs files still missing in win32 install (8.3.1) Magnus Hagander
• 14 April 2008
  • Re: BUG #3983: pgxs files still missing in win32 install (8.3.1) Joe Conway
  • Re: BUG #3983: pgxs files still missing in win32 install (8.3.1) Magnus Hagander
  • Re: BUG #4101: Fails to start when transaction log on another drive Euler Taveira de Oliveira
• 13 April 2008
  • Re: tracking down a crash bug Tom Lane
  • tracking down a crash bug Orion Henry
  • tracking down a crash bug Orion Henry
  • Re: BUG #3983: pgxs files still missing in win32 install (8.3.1) Joe Conway
  • Re: BUG #4106: WHERE - clause in view works only sometimes Alexander Strotmann
  • Re: BUG #3953: No PostGIS option in installer ChrisWebster
  • Re: BUG #4106: WHERE - clause in view works only sometimes Tom Lane
• 12 April 2008
  • Re: BUG #4106: WHERE - clause in view works only sometimes Tom Lane
  • Re: BUG #4106: WHERE - clause in view works only sometimes Heikki Linnakangas
  • BUG #4106: WHERE - clause in view works only sometimes Alexander Strotmann
  • Re: BUG #3953: No PostGIS option in installer Dave Page
  • Re: BUG #3953: No PostGIS option in installer ChrisWebster
  • Re: error php - postgresql Guillaume Smet
  • Re: operator does not exist: timestamp w/out timezone (similar to bug 3807) Guillaume Smet
  • error php - postgresql jalvarez
  • operator does not exist: timestamp w/out timezone (similar to bug 3807) philwalk
• 11 April 2008
  • Re: BUG #4104: Uninstall/remove not working correctly John R Pierce
  • BUG #4105: Service already started but no choice to stop in pgAdmin3 gui
  • BUG #4104: Uninstall/remove not working correctly alex
  • Re: BUG #4103: DELETE Syntax Error Tom Lane
  • BUG #4103: DELETE Syntax Error Yu Jye Foo
• 10 April 2008
  • BUG #4101: Fails to start when transaction log on another drive Mikel Lindsaar
  • Re: BUG #4090: ECPG Selecting table with NULL values Michael Meskes
  • Error in module Prakash Suryawanshi
  • Re: BUG #4096: PG 8.3.1. confused about remaining disk space J6M
  • Error in module Prakash Suryawanshi
• 09 April 2008
  • Re: BUG #4091: ECPG $select incompability with Informix Michael Meskes
  • Re: BUG #4091: ECPG $select incompability with Informix Bruce Momjian
• 08 April 2008
  • Re: BUG #4100: GMT offsets are wrong Tom Lane
  • Re: BUG #4096: PG 8.3.1. confused about remaining disk space J6M
  • Re: BUG #4100: GMT offsets are wrong Magnus Hagander
  • BUG #4100: GMT offsets are wrong Peter Coxhead
• 07 April 2008
  • Re: BUG #4096: PG 8.3.1. confused about remaining disk space Stefan Kaltenbrunner
  • BUG #4099: backup error felipe macedo
  • Re: BUG #4098: Encoding problems Heikki Linnakangas
  • BUG #4098: Encoding problems Jan-Peter Seifert
  • Re: BUG #4096: PG 8.3.1. confused about remaining disk space J6M
  • Re: BUG #4096: PG 8.3.1. confused about remaining disk space J6M
  • Re: BUG #4096: PG 8.3.1. confused about remaining disk space Gregory Stark
  • Re: BUG #4096: PG 8.3.1. confused about remaining disk space Gregory Stark
  • Re: BUG #4096: PG 8.3.1. confused about remaining disk space J6M
  • Re: BUG #4096: PG 8.3.1. confused about remaining disk space Tom Lane
  • Re: BUG #4096: PG 8.3.1. confused about remaining disk space J6M
  • Re: BUG #4096: PG 8.3.1. confused about remaining disk space J6M
  • BUG #4097: can join + where query be optimized? Adriaan van Kekem
  • Re: BUG #4096: PG 8.3.1. confused about remaining disk space Gregory Stark
  • Re: BUG #4096: PG 8.3.1. confused about remaining disk space Zdenek Kotala
  • BUG #4096: PG 8.3.1. confused about remaining disk space
  • Re: BUG #3983: pgxs files still missing in win32 install (8.3.1) Magnus Hagander
  • Re: CREATEDB and CREATEROLE privileges cannot vacuum pg_authid and others Tom Lane
  • CREATEDB and CREATEROLE privileges cannot vacuum pg_authid and others Gabriel Ramirez
• 06 April 2008
  • Re: BUG #3983: pgxs files still missing in win32 install (8.3.1) Joe Conway
  • Re: BUG #4095: Out of memory when restore db Tom Lane
  • Re: BUG #4090: ECPG Selecting table with NULL values Michael Meskes
  • BUG #4095: Out of memory when restore db Pavel Zaitsev
• 05 April 2008
  • Re: BUG #4092: initdb fails if the xlog directory is the same as [pg_data]/pg_xlog Tom Lane
  • Re: BUG #4084: Some DST timezones switche to summer time (one week) later Premek Paska
  • BUG #4091: ECPG $select incompability with Informix Mikael Omma
  • BUG #4090: ECPG Selecting table with NULL values Mikael Omma
• 04 April 2008
  • BUG #4092: initdb fails if the xlog directory is the same as [pg_data]/pg_xlog Peter Koczan
  • Re: BUG #4089: When available disk space is low pg_stop_backup() fails, as do subsequent recovery attempts. Tom Lane
  • Re: BUG #4089: When available disk space is low pg_stop_backup() fails, as do subsequent recovery attempts. John Smith
  • Re: [PATCHES] Re: BUG #4070: Join more then ~15 tables let postgreSQL produces wrong data Ceschia, Marcello
  • BUG #4089: When available disk space is low pg_stop_backup() fails, as do subsequent recovery attempts. John Smith
• 03 April 2008
  • Re: [PATCHES] Re: BUG #4070: Join more then ~15 tables let postgreSQL produces wrong data Tom Lane

• Thread Index
• [Prev Page]
• [Next Page]