pgsql-bugs 2010-01 Thread Index (2/2)

Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Text Size: Normal / Large
Donate
Contact

Header And Logo

PostgreSQL

|

The world's most advanced open source database.

Site Navigation

pgsql-bugs 2010-01 Thread Index (2/2)

Last updated: Wed Jan 18 01:43:13 2012
282 messages

Main Index
[Prev Page]
[Next Page]

Re: BUG #5270: escape warning even with standard behavior, (continued)
- Re: BUG #5270: escape warning even with standard behavior Tom Lane (Sun 10 05:59)
could not open server file beulah prasanthi (Sat 09 07:36)

<Possible follow-ups>
Re: could not open server file Kevin Grittner (Sun 10 15:22)

Re: could not open server file Robert Haas (Sun 10 18:40)

BUG #5269: postgres backend terminates with SIGSEGV Justin Pitts (Sat 09 03:50)

Re: BUG #5269: postgres backend terminates with SIGSEGV Tom Lane (Sat 09 04:05)

Message not available
- Message not available
  - Message not available
    - Message not available
    - Message not available
    - Message not available
    - Message not available
    - Message not available
    - Message not available
    - Message not available
    - Message not available
    - Re: BUG #5269: postgres backend terminates with SIGSEGV Tom Lane (Wed 13 04:54)
    - Re: BUG #5269: postgres backend terminates with SIGSEGV Kris Jurka (Wed 13 07:07)
    - Re: BUG #5269: postgres backend terminates with SIGSEGV Tom Lane (Wed 13 16:59)
    - Re: BUG #5269: postgres backend terminates with SIGSEGV Justin Pitts (Thu 14 03:22)
    - Re: BUG #5269: postgres backend terminates with SIGSEGV Justin Pitts (Thu 14 15:14)
    - Re: BUG #5269: postgres backend terminates with SIGSEGV Tom Lane (Thu 14 15:17)
    - Re: BUG #5269: postgres backend terminates with SIGSEGV Justin Pitts (Thu 14 15:34)
    - Re: BUG #5269: postgres backend terminates with SIGSEGV Tom Lane (Thu 14 15:45)
    - Re: BUG #5269: postgres backend terminates with SIGSEGV Justin Pitts (Thu 14 19:03)
    - Re: BUG #5269: postgres backend terminates with SIGSEGV Tom Lane (Thu 14 15:19)
    - Re: BUG #5269: postgres backend terminates with SIGSEGV Justin Pitts (Thu 14 15:26)

AIX initdb problem: /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data fails Michael Felt (Fri 08 10:08)

Re: AIX initdb problem: /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data fails Michael Felt (Fri 08 16:51)

Re: BUG #5236: Aparent bug in ecpg (postgresql 8.4 ) Michael Meskes (Fri 08 09:28)
Re: BUG #5268: PQgetvalue incorrectly returns 0 (corrected) Mark Kirkwood (Fri 08 04:47)
Re: BUG #5098: Levenshtein with costs is broken Robert Haas (Thu 07 18:18)
Concurrent update failure in HEAD Takahiro Itagaki (Thu 07 06:36)

Re: Concurrent update failure in HEAD Tom Lane (Thu 07 15:03)
Re: Concurrent update failure in HEAD Tom Lane (Fri 08 02:45)

Re: Concurrent update failure in HEAD Takahiro Itagaki (Fri 08 03:27)

email addresses Mike Landis (Thu 07 04:20)

Re: email addresses John R Pierce (Thu 07 07:13)
Re: email addresses Robert Haas (Thu 07 11:01)

Re: email addresses Alvaro Herrera (Thu 07 14:16)

Re: email addresses Robert Haas (Thu 07 15:08)

Re: email addresses Michael Felt (Fri 08 04:02)

BUG #5268: PQgetvalue incorrectly returns 0 Mike Landis (Thu 07 04:11)

Re: BUG #5268: PQgetvalue incorrectly returns 0 tomas (Thu 07 07:17)

Re: BUG #5268: PQgetvalue incorrectly returns 0 Mike Landis (Thu 07 12:53)

Re: BUG #5268: PQgetvalue incorrectly returns 0 Robert Haas (Thu 07 18:02)

Re: BUG #5268: PQgetvalue incorrectly returns 0 Tom Lane (Thu 07 13:07)
<Possible follow-ups>
Re: BUG #5268: PQgetvalue incorrectly returns 0 Mike Landis (Thu 07 20:21)

Re: BUG #5268: PQgetvalue incorrectly returns 0 Alvaro Herrera (Fri 08 00:07)
Re: BUG #5268: PQgetvalue incorrectly returns 0 Mark Kirkwood (Fri 08 00:31)

Re: BUG #5268: PQgetvalue incorrectly returns 0 Robert Haas (Fri 08 02:18)

Re: BUG #5268: PQgetvalue incorrectly returns 0 Mark Kirkwood (Fri 08 05:51)

BUG #5267: initdb fails on AIX: could not identify current directory Michael Felt (Wed 06 12:11)

Re: BUG #5267: initdb fails on AIX: could not identify current directory Michael Felt (Wed 06 12:16)
Re: BUG #5267: initdb fails on AIX: could not identify current directory Alvaro Herrera (Wed 06 15:19)
Re: BUG #5267: initdb fails on AIX: could not identify current directory Tom Lane (Wed 06 17:41)

Re: BUG #5267: initdb fails on AIX: could not identify current directory Michael Felt (Thu 07 14:29)

Re: BUG #5267: initdb fails on AIX: could not identify current directory Tom Lane (Thu 07 14:36)

Re: BUG #5267: initdb fails on AIX: could not identify current directory Michael Felt (Thu 07 14:42)

Re: BUG #5267: initdb fails on AIX: could not identify current directory Tom Lane (Thu 07 14:57)
Re: BUG #5267: initdb fails on AIX: could not identify current directory Michael Felt (Thu 07 15:08)
Re: BUG #5267: initdb fails on AIX: could not identify current directory Robert Haas (Thu 07 15:25)
Re: BUG #5267: initdb fails on AIX: could not identify current directory Michael Felt (Thu 07 15:47)
Re: BUG #5267: initdb fails on AIX: could not identify current directory Tom Lane (Thu 07 16:43)
Re: BUG #5267: initdb fails on AIX: could not identify current directory Tom Lane (Thu 07 16:40)
Re: BUG #5267: initdb fails on AIX: could not identify current directory Robert Haas (Thu 07 18:04)
Re: BUG #5267: initdb fails on AIX: could not identify current directory Tom Lane (Thu 07 18:43)
Message not available
Message not available
Re: BUG #5267: initdb fails on AIX: could not identify current directory Michael Felt (Mon 11 07:57)
Re: BUG #5267: initdb fails on AIX: could not identify current directory Michael Felt (Thu 07 16:11)

BUG #5266: erros no servidor web robson (Tue 05 19:21)

Re: BUG #5266: erros no servidor web tomas (Wed 06 08:51)

BUG #5265: incomplete startup packet AI Rumman (Tue 05 12:23)

Re: BUG #5265: incomplete startup packet Alvaro Herrera (Tue 05 12:42)

BUG #5264: could not create shared memory segment: Invalid argument venkat nemani (Tue 05 07:06)

Re: BUG #5264: could not create shared memory segment: Invalid argument Craig Ringer (Tue 05 10:26)

BUG #5263: Query execution fails with "ERROR: FULL JOIN is only supported with merge-joinable join conditions" Jozsef Szalay (Tue 05 01:43)

Re: BUG #5263: Query execution fails with "ERROR: FULL JOIN is only supported with merge-joinable join conditions" Tom Lane (Tue 05 21:17)

Re: BUG #5263: Query execution fails with "ERROR: FULL JOIN is only supported with merge-joinable join conditions" Jozsef Szalay (Tue 05 22:26)

Re: BUG #5263: Query execution fails with "ERROR: FULL JOIN is only supported with merge-joinable join conditions" Tom Lane (Tue 05 23:35)

BUG #5261: Invalide page header Takesver Kumar Thakur (Mon 04 13:44)

Re: BUG #5261: Invalide page header Robert Haas (Mon 04 19:33)

BUG #5260: Postgre crashed unexpectedly Toni Helenius (Mon 04 10:30)

Re: BUG #5260: Postgre crashed unexpectedly Robert Haas (Mon 04 17:24)

BUG #5259: the table name double David (Mon 04 06:26)

Re: BUG #5259: the table name double Craig Ringer (Mon 04 07:50)

Re: BUG #5259: the table name double Tom Lane (Mon 04 17:55)

Message not available
- Re: BUG #5259: the table name double Craig Ringer (Mon 04 11:26)

BUG #5258: Unique and foreign key constraints fail on columns with reserved names, but not check constraints Ben Woosley (Mon 04 03:49)

Re: BUG #5258: Unique and foreign key constraints fail on columns with reserved names, but not check constraints Jasen Betts (Mon 04 10:07)
Re: BUG #5258: Unique and foreign key constraints fail on columns with reserved names, but not check constraints Peter Eisentraut (Mon 04 10:36)

Re: BUG #5258: Unique and foreign key constraints fail on columns with reserved names, but not check constraints Ben Woosley (Mon 04 17:58)

Re: BUG #5258: Unique and foreign key constraints fail on columns with reserved names, but not check constraints Tom Lane (Mon 04 18:31)

Re: BUG #5258: Unique and foreign key constraints fail on columns with reserved names, but not check constraints Ben Woosley (Mon 04 18:39)

Re: BUG #5258: Unique and foreign key constraints fail on columns with reserved names, but not check constraints Robert Haas (Mon 04 18:13)

Failed to run initdb - not resolved bug 5130 Tomas Studva (Sat 02 21:50)

Re: Failed to run initdb - not resolved bug 5130 John R Pierce (Sat 02 22:59)

Re: Failed to run initdb - not resolved bug 5130 Tomas Studva (Sat 02 23:28)
Re: Failed to run initdb - not resolved bug 5130 Craig Ringer (Sun 03 02:33)

Re: Failed to run initdb - not resolved bug 5130 Robert Haas (Mon 04 17:21)

Re: Failed to run initdb - not resolved bug 5130 Tomas Studva (Tue 26 22:01)

Re: Failed to run initdb - not resolved bug 5130 Euler Taveira de Oliveira (Wed 27 00:32)

<Possible follow-ups>
Failed to run initdb - not resolved bug 5130 Tomas Studva (Sat 02 21:53)
Re: Failed to run initdb - not resolved bug 5130 Thomas Specker (Tue 12 13:31)

Re: Failed to run initdb - not resolved bug 5130 Robert Haas (Fri 15 16:51)

test message Tomas Studva (Sat 02 21:45)
BUG #5257: wrong results of SUBSTRING with SQL regular expressions Roman Kononov (Sat 02 19:30)

Re: BUG #5257: wrong results of SUBSTRING with SQL regular expressions Tom Lane (Sat 02 20:01)
Re: BUG #5257: wrong results of SUBSTRING with SQL regular expressions Roman Kononov (Sat 02 22:26)

Error in exclusion constraint error message (8.5)? hubert depesz lubaczewski (Sat 02 13:37)

Re: Error in exclusion constraint error message (8.5)? Tom Lane (Sat 02 17:55)
Re: Error in exclusion constraint error message (8.5)? Greg Stark (Sat 02 18:37)

Re: Error in exclusion constraint error message (8.5)? Tom Lane (Sat 02 19:23)

Main Index
[Prev Page]
[Next Page]

Mail converted by MHonArc

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group