• 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-general
    • pgsql-jobs
    • pgsql-novice
    • pgsql-performance
    • pgsql-php
    • pgsql-sql
    • pgsql-students
  • Developer lists
  • Regional lists
  • Associations
  • User groups
  • Project lists
  • Inactive lists
• IRC
• Featured Users
• International Sites
• Propaganda
• Resources
• Weekly News
• Community login
  • Profile
  • Lost password

pgsql-bugs 2008-05 Chronological Index (2/2)

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

• 09 May 2008
  • BUG #4150: ecpg: update/insert of array data does not work anymore since Version 8.2 Christian Lippuner (17:02)
• 08 May 2008
  • Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Aleksej Saushev (17:24)
  • Re: Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Andrew Chernow (17:03)
  • Re: Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Merlin Moncure (16:44)
  • Re: Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Bruce Momjian (16:27)
  • Re: Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Aleksej Saushev (16:17)
  • Re: Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Andrew Chernow (15:55)
  • Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Bruce Momjian (15:35)
  • Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Merlin Moncure (14:16)
  • Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Andrew Chernow (02:37)
  • Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Bruce Momjian (02:21)
  • Re: BUG #4040: psql should provide option to not prompt for password Bruce Momjian (01:28)
  • Re: BUG #4040: psql should provide option to not prompt for password Bruce Momjian (00:28)
• 07 May 2008
  • Re: BUG: aliases does not work (( Tom Lane (16:32)
  • Re: BUG: aliases does not work (( Eugen.Konkov (16:16)
  • Re: BUG #4148: tsearch related issue Tom Lane (15:10)
  • Re: BUG #4024: xpath() results lose namespace mappings Bruce Momjian (14:43)
  • ORDER BY...LIMIT optimization does not work with inherited tables Marshall, Steve (12:50)
  • Re: BUG: aliases does not work (( Peter Eisentraut (11:52)
  • BUG: aliases does not work (( Eugen.Konkov (11:40)
  • BUG #4148: tsearch related issue (08:37)
• 06 May 2008
  • BUG #4147: pg_constraint table data retrieval error Arun J M (11:02)
  • Re: BUG #4137: Postgres drives pg_standby %r param to delete WAL file before processing Simon Riggs (08:11)
• 05 May 2008
  • Re: Feature request Pavel Stehule (19:40)
  • Re: Feature request Eugen.Konkov (17:26)
  • Re: Feature request Pavel Stehule (17:10)
  • Feature request Eugen.Konkov (16:42)
  • BUG #4145: org.postgresql.util.PSQLException: An I/O error occured while sending to the backend. P.Senthil Kumar (12:49)
• 04 May 2008
  • Re: BUG #4142: pg_dump will not work Magnus Hagander (14:39)
  • BUG #4142: pg_dump will not work Lee Ottaway (12:04)
• 03 May 2008
  • Re: BUG #4141: Aliases in rules vanished, but they work Tom Lane (21:53)
  • BUG #4141: Aliases in rules vanished, but they work Mathias Seiler (21:27)
  • Re: BUG #4137: Postgres drives pg_standby %r param to delete WAL file before processing Simon Riggs (11:27)
• 02 May 2008
  • Re: BUG #4137: Postgres drives pg_standby %r param to delete WAL file before processing Simon Riggs (21:00)
  • BUG #4137: Postgres drives pg_standby %r param to delete WAL file before processing Wojciech Strzalka (18:11)
• 01 May 2008
  • Re: BUG #4135: postmaster crashes if matching on VALUES is used on a column with index Tom Lane (14:30)
• 30 April 2008
  • BUG #4135: postmaster crashes if matching on VALUES is used on a column with index Miernik (21:58)

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