• 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-05 Thread Index (2/2)

• Main Index
• [Prev Page]
• [Next Page]

• BUG #4150: ecpg: update/insert of array data does not work anymore since Version 8.2 Christian Lippuner
• Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Bruce Momjian
• Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Andrew Chernow
• <Possible follow-ups>
• Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Merlin Moncure
• Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Aleksej Saushev
• Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Bruce Momjian
• Re: Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Andrew Chernow
• Re: Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Aleksej Saushev
• Re: Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Bruce Momjian
• Re: Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Merlin Moncure
• Re: Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order Andrew Chernow
• Re: BUG #4040: psql should provide option to not prompt for password Bruce Momjian
• <Possible follow-ups>
• Re: BUG #4040: psql should provide option to not prompt for password Bruce Momjian
• Re: BUG #4024: xpath() results lose namespace mappings Bruce Momjian
• ORDER BY...LIMIT optimization does not work with inherited tables Marshall, Steve
• BUG: aliases does not work (( Eugen.Konkov
• Re: BUG: aliases does not work (( Peter Eisentraut
• Re: BUG: aliases does not work (( Eugen.Konkov
• Re: BUG: aliases does not work (( Tom Lane
• BUG #4148: tsearch related issue
• Re: BUG #4148: tsearch related issue Tom Lane
• BUG #4147: pg_constraint table data retrieval error Arun J M
• Feature request Eugen.Konkov
• Re: Feature request Pavel Stehule
• Re: Feature request Eugen.Konkov
• Re: Feature request Pavel Stehule
• BUG #4145: org.postgresql.util.PSQLException: An I/O error occured while sending to the backend. P.Senthil Kumar
• BUG #4142: pg_dump will not work Lee Ottaway
• Re: BUG #4142: pg_dump will not work Magnus Hagander
• BUG #4141: Aliases in rules vanished, but they work Mathias Seiler
• Re: BUG #4141: Aliases in rules vanished, but they work Tom Lane
• BUG #4137: Postgres drives pg_standby %r param to delete WAL file before processing Wojciech Strzalka
• Re: BUG #4137: Postgres drives pg_standby %r param to delete WAL file before processing Simon Riggs
• Re: BUG #4137: Postgres drives pg_standby %r param to delete WAL file before processing Simon Riggs
• Message not available
  • Re: BUG #4137: Postgres drives pg_standby %r param to delete WAL file before processing Simon Riggs
• BUG #4135: postmaster crashes if matching on VALUES is used on a column with index Miernik
• Re: BUG #4135: postmaster crashes if matching on VALUES is used on a column with index Tom Lane

---

• Main Index
• [Prev Page]
• [Next Page]

---

Mail converted by MHonArc