• 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-02 Chronological Index (2/2)

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

• 11 February 2008
  • Re: BUG #3948: date/time functions returning wrong value Magnus Hagander
  • Re: BUG #3948: date/time functions returning wrong value Magnus Hagander
  • Re: BUG #3948: date/time functions returning wrong value Tom Lane
  • Re: BUG #3948: date/time functions returning wrong value Alvaro Herrera
• 10 February 2008
  • Re: BUG #3951: SELECT ... WHERE Param = ? does not work if Param is of type bytea Gevik Babakhani
  • Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size" Tom Lane
  • Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size" Tomas Szepe
  • Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size" Tom Lane
  • Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size" Tomas Szepe
  • BUG #3951: SELECT ... WHERE Param = ? does not work if Param is of type bytea vha
  • Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size" Tom Lane
  • Re: BUG #3947: Unable to Initialize Data Cluster Dave Page
  • Re: BUG #3950: Server Problems Tom Lane
  • Re: BUG #3947: Unable to Initialize Data Cluster Dave Page
  • Re: BUG #3947: Unable to Initialize Data Cluster Dave Page
  • BUG #3950: Server Problems Wolvesden
  • Re: BUG #3948: date/time functions returning wrong value Magnus Hagander
  • Re: BUG #3948: date/time functions returning wrong value Jorge Campins
  • Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size" Tomas Szepe
  • Re: BUG #3948: date/time functions returning wrong value Magnus Hagander
  • Re: BUG #3948: date/time functions returning wrong value Magnus Hagander
  • Re: BUG #3945: unexpected ON INSERT rule behaviour Gurjeet Singh
  • Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size" Tom Lane
  • Re: BUG #3948: date/time functions returning wrong value Jorge Campins
  • Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size" Tomas Szepe
  • Re: BUG #3948: date/time functions returning wrong value Tom Lane
  • Re: BUG #3948: date/time functions returning wrong value Magnus Hagander
• 09 February 2008
  • BUG #3948: date/time functions returning wrong value Jorge Campins
  • Re: BUG #3947: Unable to Initialize Data Cluster Dave Page
  • Re: BUG #3947: Unable to Initialize Data Cluster Dave Page
  • BUG #3947: Unable to Initialize Data Cluster Lee Ottaway
  • Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size" Tom Lane
  • 8.3.0: vacuum full analyze: "invalid memory alloc request size" Tomas Szepe
• 08 February 2008
  • BUG #3945: unexpected ON INSERT rule behaviour Holger Klawitter
  • Re: BUG #3944: Unable to create a database using SQL_ASCII encoding Heikki Linnakangas
  • Re: BUG #3944: Unable to create a database using SQL_ASCII encoding Tom Lane
  • Re: BUG #3943: ecpg doesn't like "inet" operator Tom Lane
  • BUG #3944: Unable to create a database using SQL_ASCII encoding Dan Hrabarchuk
  • BUG #3943: ecpg doesn't like "inet" operator Arnaud
  • Re: BUG #3942: Related to BUG #2568 and BUG #2859: VACUUM process hangs and does not respond to the kill signals Heikki Linnakangas
  • BUG #3942: Related to BUG #2568 and BUG #2859: VACUUM process hangs and does not respond to the kill signals Valentine Gogichashvili
  • Re: Re: BUG #3924: Create Database with another encoding as the encoding from postgres Heikki Linnakangas
  • Re: BUG #3941: Insert Error Gary Doades
  • Re: BUG #3941: Insert Error Zdenek Kotala
  • BUG #3941: Insert Error gnp yadav
• 07 February 2008
  • Re: BUG #3940: 'unrecognized node type: 1718580065' Tom Lane
  • Re: BUG #3938: Row-wise comparison fails Tom Lane
  • BUG #3940: 'unrecognized node type: 1718580065' Vladimir Kokovic
  • Re: BUG #3938: Row-wise comparison fails Tom Lane
  • Re: [HACKERS] possible bug windows setup Andrew Dunstan
  • Re: [HACKERS] possible bug windows setup Magnus Hagander
  • Re: [HACKERS] possible bug windows setup Andrew Dunstan
  • Re: BUG #3938: Row-wise comparison fails Alvaro Herrera
  • Re: BUG #3939: (Possibly) no NLS in 8.3 Windows Magnus Hagander
  • Re: possible bug windows setup Magnus Hagander
  • BUG #3939: (Possibly) no NLS in 8.3 Windows Gevik Babakhani
  • BUG #3938: Row-wise comparison fails
• 06 February 2008
  • Re: BUG #3937: timestamp null value comparison in subquery using IN/NOT IN Tom Lane
  • BUG #3937: timestamp null value comparison in subquery using IN/NOT IN Jan Mate
  • Re: Vers. 8.3.0: "make check" fails dismally Tom Lane
  • Re: BUG #3924: Create Database with another encoding as the encoding from postgres Pit M.
  • Re: Vers. 8.3.0: "make check" fails dismally Peter Eisentraut
  • possible bug windows setup Gevik Babakhani
  • Vers. 8.3.0: "make check" fails dismally Mike Dowling
  • BUG #3936: don't supporting case-insensitive regexp in russian UTF-8 encoding Kirill
  • Re: BUG #3935: about Unicode values Michael Fuhr
  • BUG #3935: about Unicode values Vaibhav More
  • BUG #3934: Connection error in CGI Script Ram Vinay Pandey
• 05 February 2008
  • Re: BUG #3928: INFORMATION_SCHEMA does not give results if a user is allowed only access via ROLE Tom Lane
  • Re: BUG #3933: Update problem for 3 Foreign Keys referencing 1 field in another table (I'm not newbie in using SQL) Heikki Linnakangas
  • BUG #3933: Update problem for 3 Foreign Keys referencing 1 field in another table (I'm not newbie in using SQL) irfin
  • Re: BUG #3929: RULE causes unintended update of SEQUENCE Tom Lane
  • Re: BUG #3932: utf-8 and upper()/lower(): PANIC: ERRORDATA_STACK_SIZE exceeded Florian Wunderlich
  • Re: BUG #3932: utf-8 and upper()/lower(): PANIC: ERRORDATA_STACK_SIZE exceeded Alvaro Herrera
  • BUG #3932: utf-8 and upper()/lower(): PANIC: ERRORDATA_STACK_SIZE exceeded Florian Wunderlich
  • BUG #3931: problems in the install process Rafael Aguilar
  • Re: BUG #3930: initdb failed - "postgres" not found Dave Page
  • BUG #3930: initdb failed - "postgres" not found Markus Eisenmann
  • BUG #3929: RULE causes unintended update of SEQUENCE Arjan Tuinhout
  • BUG #3928: INFORMATION_SCHEMA does not give results if a user is allowed only access via ROLE Bart Heupers
  • Re: BUG #3927: configure --with-gssapi fails Christian Ullrich
• 04 February 2008
  • Re: BUG #3927: configure --with-gssapi fails Tom Lane
  • Re: BUG #3927: configure --with-gssapi fails Christian Ullrich
  • BUG #3927: configure --with-gssapi fails Christian Ullrich
• 03 February 2008
  • Re: BUG #3926: Typo in documentation Tom Lane
  • BUG #3926: Typo in documentation Andreas
• 02 February 2008
  • Re: BUG #3925: You can delete enum elements from pg_enum, but it is used in a table Tom Lane
  • Re: BUG #3924: Create Database with another encoding as the encoding from postgres Heikki Linnakangas
  • Re: BUG #3924: Create Database with another encoding as the encoding from postgres Peter Eisentraut
  • BUG #3925: You can delete enum elements from pg_enum, but it is used in a table Stefan Kunick
  • BUG #3924: Create Database with another encoding as the encoding from postgres Stefan Kunick
  • Re: BUG #3922: Problems migrating databases. Peter Eisentraut
  • Re: BUG #3920: sequence not generated for postgres using toplink jpa Arun ViswanathanChandrika
• 01 February 2008
  • BUG #3922: Problems migrating databases. Maximiliano
  • Re: BUG #3921: CREATE TABLE / INCLUDING INDEXES fails with permission denied Gregory Stark
  • Re: BUG #3921: CREATE TABLE / INCLUDING INDEXES fails with permission denied Tom Lane
  • Re: BUG #3894: JDBC DatabaseMetaData.getTables is inconsistently case-sensitive with schema name Kris Jurka
  • BUG #3921: CREATE TABLE / INCLUDING INDEXES fails with permission denied Andrew Gilligan
  • Re: BUG #3894: JDBC DatabaseMetaData.getTables is inconsistently case-sensitive with schema name Adam Hardy
  • BUG #3920: sequence not generated for postgres using toplink jpa Arun
  • BUG #3919: Service Privileges Bug Sergey

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