• 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-03 Chronological Index (1/3)

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

• 31 March 2008
  • Re: BUG #4074: Using SESSION_USER or CURRENT_USER in a view definition is unsafe Alvaro Herrera
  • Re: BUG #4074: Using SESSION_USER or CURRENT_USER in a view definition is unsafe Lars E. Olson
  • Re: BUG #4074: Using SESSION_USER or CURRENT_USER in a view definition is unsafe Dave Page
  • Re: BUG #4074: Using SESSION_USER or CURRENT_USER in a view definition is unsafe Tom Lane
  • Re: BUG #4073: ERROR: invalid input syntax for type timestamp: "Sat Mar 29 04:47:06 WEST 2008" Tom Lane
  • Re: BUG #4074: Using SESSION_USER or CURRENT_USER in a view definition is unsafe Heikki Linnakangas
  • Re: BUG #4073: ERROR: invalid input syntax for type timestamp: "Sat Mar 29 04:47:06 WEST 2008" Heikki Linnakangas
  • BUG #4074: Using SESSION_USER or CURRENT_USER in a view definition is unsafe Lars Olson
  • BUG #4073: ERROR: invalid input syntax for type timestamp: "Sat Mar 29 04:47:06 WEST 2008" Pedro Alves
  • Re: BUG #4069: Wrong tip Chris Browne
  • Re: BUG #4070: Join more then ~15 tables let postgreSQL produces wrong data Heikki Linnakangas
  • Re: BUG #4070: Join more then ~15 tables let postgreSQL produces wrong data Heikki Linnakangas
  • BUG #4070: Join more then ~15 tables let postgreSQL produces wrong data Marcello Ceschia
  • Re: Recommended approach for upgrading DBs with nonmatching encodings Tom Lane
  • Re: Recommended approach for upgrading DBs with nonmatching encodings Martin Pitt
• 30 March 2008
  • Re: Recommended approach for upgrading DBs with nonmatching encodings Tom Lane
  • Re: Recommended approach for upgrading DBs with nonmatching encodings Martin Pitt
  • Re: Recommended approach for upgrading DBs with nonmatching encodings Tom Lane
  • Re: Recommended approach for upgrading DBs with nonmatching encodings Martin Pitt
  • Recommended approach for upgrading DBs with nonmatching encodings Martin Pitt
  • Re: The problem with FULL JOIN Stephan Szabo
  • Re: The problem with FULL JOIN Gregory Stark
  • Re: BUG #4069: Wrong tip Gregory Stark
  • The problem with FULL JOIN Eugen.Konkov
  • Re: BUG #4069: Wrong tip Dave Page
  • Re: Workaround to get arrays for plperl Eugen.Konkov
  • Re: Workaround to get arrays for plperl CaT
  • Workaround to get arrays for plperl Eugen.Konkov
  • BUG #4069: Wrong tip Eduard Fernandez-Diaz
• 29 March 2008
  • Apologies (Re: University of Bridgeport Graduate Programs and Research Opportunities) Andrew Sullivan
  • Re: BUG #3980: Can not Install PostgreSQL - error at the end of installation Aaron Tuwhangai
• 28 March 2008
  • Re: 8.3 problems with sspi authentication Magnus Hagander
  • Re: ERROR: RETURN NEXT must specify a record or row variable in function returning tuple Eugen.Konkov
  • Re: BUG: wrong doc or wrong connectby? Alvaro Herrera
  • ERROR: RETURN NEXT must specify a record or row variable in function returning tuple Eugen.Konkov
  • Re: FOR-IN-EXECUTE: FOR does not replanned on each entry to the FOR loop Eugen.Konkov
  • Re: BUG: wrong doc or wrong connectby? Eugen.Konkov
  • Re: Redundant explicit field name/types description while select from function with return type of record Sam Mason
  • Re: Redundant explicit field name/types description while select from function with return type of record Euler Taveira de Oliveira
  • Re: FOR-IN-EXECUTE: FOR does not replanned on each entry to the FOR loop Euler Taveira de Oliveira
  • Re: [PATCHES] Incomplete docs for restore_command for hotstandby Bruce Momjian
  • Re: Problem identifying constraints which should not be inherited Alex Hunsaker
  • Re: [PATCHES] Incomplete docs for restore_command for hotstandby Heikki Linnakangas
  • Re: FOR-IN-EXECUTE: FOR does not replanned on each entry to the FOR loop Tom Lane
  • Re: Redundant explicit field name/types description while select from function with return type of record Tom Lane
  • Re: BUG: wrong doc or wrong connectby? Tom Lane
  • BUG: wrong doc or wrong connectby? Eugen.Konkov
  • Re: Problem identifying constraints which should not be inherited Alvaro Herrera
  • Re: [PATCHES] Incomplete docs for restore_command for hot standby Simon Riggs
  • Re: Problem identifying constraints which should not be inherited Alvaro Herrera
  • FOR-IN-EXECUTE: FOR does not replanned on each entry to the FOR loop Eugen.Konkov
  • Documentation commenting does not work Eugen.Konkov
  • Re: Problem identifying constraints which should not be inherited NikhilS
  • Redundant explicit field name/types description while select from function with return type of record Eugen.Konkov
  • University of Bridgeport Graduate Programs and Research Opportunities University of Bridgeport
• 27 March 2008
  • Re: problem with silent installation acordner
  • Re: BUG #4068: Failed to compile 8.3.1 Tom Lane
  • Re: BUG #4068: Failed to compile 8.3.1 Ronald Kuczek
  • Re: BUG #4068: Failed to compile 8.3.1 Ronald Kuczek
  • Re: BUG #4068: Failed to compile 8.3.1 Tom Lane
  • Re: BUG #4068: Failed to compile 8.3.1 Alvaro Herrera
  • Re: BUG #4059: Vacuum full not always cleaning empty tables Alvaro Herrera
  • Re: BUG #4068: Failed to compile 8.3.1 Ronald Kuczek
  • Re: BUG #4068: Failed to compile 8.3.1 Bruce Momjian
  • Re: BUG #4068: Failed to compile 8.3.1 Alvaro Herrera
  • Re: BUG #4068: Failed to compile 8.3.1 Alvaro Herrera
  • Re: BUG #4068: Failed to compile 8.3.1 Ronald Kuczek
  • Re: BUG #4068: Failed to compile 8.3.1 Tom Lane
  • Re: BUG #4068: Failed to compile 8.3.1 Ronald Kuczek
  • Re: BUG #4068: Failed to compile 8.3.1 Zdenek Kotala
  • Re: DISTINCT MAX() results mismatch on 8.2 and 8.3 Tom Lane
  • Re: BUG #4056: problem creating function with domain argument Dave Page
  • BUG #4068: Failed to compile 8.3.1 Ronald Kuczek
  • Re: BUG #4056: problem creating function with domain argument Eric P. Melbardis
  • Re: BUG #4056: problem creating function with domain argument Tom Lane
  • Re: Extra empty lines PGv8.3.1 Eugen.Konkov
  • Re: Extra empty lines PGv8.3.1 Alvaro Herrera
  • Re: BUG #4056: problem creating function with domain argument Dave Page
  • Extra empty lines PGv8.3.1 Eugen.Konkov
  • Re: Problem identifying constraints which should not be inherited Tom Lane
  • Re: Problem identifying constraints which should not be inherited Heikki Linnakangas
  • Re: Problem identifying constraints which should not be inherited NikhilS
  • BUG #4066: error javier redolfi
  • Re: DISTINCT MAX() results mismatch on 8.2 and 8.3 Tom Lane
  • BUG #4065: Error on psql windows client Nahum Castro
  • postgres geometry column data visibility Dr.D.D.Karunarathne
  • DISTINCT MAX() results mismatch on 8.2 and 8.3 Taiki Yamaguchi
  • BUG #4064: the 'PostgreSQL Database Server 8.3' service auto shutdown saturn five
• 26 March 2008
  • BUG #4063: psql locks up on pager during dump restore John Whitley
  • Re: BUG #4061: after backup/restore pg_attrdef.adsrc column lacks schema name. Tom Lane
  • Re: BUG: PG do not use index Bill Moran
  • Re: BUG #4059: Vacuum full not always cleaning empty tables Alvaro Herrera
  • Re: BUG #4059: Vacuum full not always cleaning empty tables Mark Steben
  • Re: BUG: PG do not use index Eugen.Konkov
  • Re: BUG: PG do not use index Tomasz Ostrowski
  • BUG #4061: after backup/restore pg_attrdef.adsrc column lacks schema name. Julius Tuskenis
  • Re: BUG: PG do not use index Eugen.Konkov
  • Re: BUG: PG do not use index Eugen.Konkov
  • Re: BUG: PG do not use index Eugen.Konkov
  • Re: BUG #4059: Vacuum full not always cleaning empty tables Alvaro Herrera
  • Re: BUG #4058: xml_table() segfaults on null Tom Lane
  • Re: Possible problem with EXTRACT(EPOCH FROM TIMESTAMP) David Rowley
  • Re: BUG #4057: SUM returns NULL when given no rows Tom Lane
• 25 March 2008
  • Re: Possible problem with EXTRACT(EPOCH FROM TIMESTAMP) Tom Lane
  • BUG #4060: libpq - large stack causes TCP/IP error Bruce Nairn
  • BUG #4059: Vacuum full not always cleaning empty tables Mark Steben
  • Re: Possible problem with EXTRACT(EPOCH FROM TIMESTAMP) David Fetter
  • Possible problem with EXTRACT(EPOCH FROM TIMESTAMP) David Rowley
  • BUG #4058: xml_table() segfaults on null Frank F.
  • Re: can't delete record from second table in rules of view with join select Tom Lane
  • Re: BUG: PG do not use index Bill Moran
  • Re: BUG #4055: Using Like in PostgreSQL 8.2.7 and 8.3.1 Bill Moran
  • Re: why provide cross type arithmetic operators Bruce Momjian
  • Re: can't delete record from second table in rules of view with join select Sergey Burladyan
  • Re: BUG: PG do not use index Alvaro Herrera
  • can't delete record from second table in rules of view with join select Sergey Burladyan
  • BUG #4057: SUM returns NULL when given no rows Reginald Drake
  • BUG: PG do not use index Eugen.Konkov
  • Re: BUG #4047: case preserve for columns Eugen.Konkov
  • Re: BUG #4056: problem creating function with domain argument Tom Lane
  • Re: why provide cross type arithmetic operators Tom Lane
  • Re: why provide cross type arithmetic operators Bruce Momjian
  • Re: BUG #3883: Autovacuum deadlock with truncate? Bruce Momjian
  • BUG #4056: problem creating function with domain argument eric melbardis
  • Re: BUG #3855: backend sends corrupted data onEHOSTDOWNerror Bruce Momjian
  • Re: BUG #3692: Conflicting create table statements throw unexpected error Bruce Momjian
  • Re: BUG #3645: regular expression back references seem broken Bruce Momjian
• 24 March 2008
  • Re: BUG #4055: Using Like in PostgreSQL 8.2.7 and 8.3.1 Alvaro Herrera
  • BUG #4055: Using Like in PostgreSQL 8.2.7 and 8.3.1 Hugo Rafael Lesme Marquez
  • Re: BUG #4054: Text containing ';' upsets db restores Tom Lane
  • BUG #4054: Text containing ';' upsets db restores Martin Gregorie
  • BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Aleksej Saushev
  • Re: BUG #4052: GCC update -fwrapv and new -Wstrict-overflow Tom Lane
  • BUG #4052: GCC update -fwrapv and new -Wstrict-overflow
  • Re: BUG #4051: ERROR: relation with OID xxxx does not exist Pavan Deolasee
  • BUG #4051: ERROR: relation with OID xxxx does not exist N Jagan Mohan Rao
  • Re: BUG #4047: case preserve for columns Eugen.Konkov
• 22 March 2008
  • Re: BUG #3983: pgxs files missing from binary installation Bruce Momjian
  • Re: BUG #4050: pg_dump data contains COMMIT statement (8.3, 8.4) Tom Lane
  • BUG #4050: pg_dump data contains COMMIT statement (8.3, 8.4) Vladimir Kokovic
  • BUG #4049: ecpg library causes signal 11 when --enable-thread-safety is turned on Steve Clark
  • Re: BUG #3833: Index remains when table is dropped Bruce Momjian
• 21 March 2008
  • Re: BUG #3822: Nonstandard precedence for comparison operators Bruce Momjian
  • Re: Server does not start when log_statement_stats is set to on Bruce Momjian
  • Re: BUG #4048: Can't install pltcl Dave Page
  • BUG #4048: Can't install pltcl IP
  • Re: BUG #4047: case preserve for columns Eugen.Konkov
  • Re: BUG #4047: case preserve for columns Tom Lane
  • subscribe Eugen.Konkov
  • Re: BUG #4047: case preserve for columns Eugen.Konkov
  • Re: BUG #4047: case preserve for columns Eugen.Konkov
  • Re: BUG #4047: case preserve for columns John R Pierce
  • BUG #4047: case preserve for columns Eugen Konkov
• 20 March 2008
  • Re: BUG #4044: Incorrect RegExp substring Output Tom Lane
  • Re: BUG #4044: Incorrect RegExp substring Output Rui Martins
  • Re: Problem identifying constraints which should not be inherited Tom Lane
  • Re: BUG #4044: Incorrect RegExp substring Output Tom Lane
  • Re: Problem identifying constraints which should not be inherited NikhilS
  • Re: Problem identifying constraints which should not be inherited Alvaro Herrera
  • Re: BUG #4044: Incorrect RegExp substring Output Rui Martins
  • Re: 8.3 can't convert cyrillic text from 'iso-8859-5' to other cyrillic 8-bit encoding Heikki Linnakangas
  • Re: Problem identifying constraints which should not be inherited NikhilS
  • Re: 8.3 can't convert cyrillic text from 'iso-8859-5' to other cyrillic 8-bit encoding Sergey Burladyan
• 19 March 2008
  • Re: 8.3 can't convert cyrillic text from 'iso-8859-5' to other cyrillic 8-bit encoding Heikki Linnakangas
  • Re: BUG #4044: Incorrect RegExp substring Output Tom Lane
  • Re: BUG #4044: Incorrect RegExp substring Output Rui Martins
  • Re: Problem identifying constraints which should not be inherited Tom Lane
  • Re: BUG #4044: Incorrect RegExp substring Output Tom Lane
  • Re: BUG #4044: Incorrect RegExp substring Output Rui Martins
  • Re: BUG #4044: Incorrect RegExp substring Output Rui Martins
  • Re: 8.3 can't convert cyrillic text from 'iso-8859-5' to other cyrillic 8-bit encoding Heikki Linnakangas
  • Re: Problem identifying constraints which should not be inherited NikhilS
  • BUG #4046: Error on connection kusum
• 18 March 2008
  • Re: BUG #4044: Incorrect RegExp substring Output Tom Lane
  • Re: BUG #4041: error in Application Stack Builder Chan, Keith \(LESA IT\)
  • Re: BUG #4041: error in Application Stack Builder Dave Page
  • BUG #4044: Incorrect RegExp substring Output Rui Martins
  • Re: BUG #4043: Unrecognized node type: using plpgsql Alvaro Herrera
  • Re: BUG #3818: Cross compilation problems Bruce Momjian
  • BUG #4043: Unrecognized node type: using plpgsql Reinier Suurenbroek

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