Re: [BUGS] BUG #5354: Type timestamptz doesn't allow to store time zone

2010-03-01 Thread Robert Haas
On Mon, Mar 1, 2010 at 10:52 AM, Vitali wrote: > > The following bug has been logged online: > > Bug reference:      5354 > Logged by:          Vitali > Email address:      vit...@lumensoftware.com > PostgreSQL version: 8.1.x 8.2.x > Operating system:   Windows, Linux > Description:        Type ti

Re: [BUGS] BUG #5355: locale incorrectly comma-separates "(null)"

2010-03-01 Thread Heikki Linnakangas
Heikki Linnakangas wrote: > Andy Lester wrote: >> The following bug has been logged online: >> >> Bug reference: 5355 >> Logged by: Andy Lester >> Email address: a...@petdance.com >> PostgreSQL version: 8.3.6 >> Operating system: Linux >> Description:locale incorrectly

Re: [BUGS] BUG #5356: citext not acting like case insensitive search

2010-03-01 Thread David E. Wheeler
On Mar 1, 2010, at 10:25 AM, Tom Lane wrote: > Not sure if there is anything we can do to make this much nicer. > Removing the implicit cast seems like a cure worse than the disease, > particularly because it would result in throwing a "no such operator" > error rather than actually doing what Mic

Re: [BUGS] BUG #5355: locale incorrectly comma-separates "(null)"

2010-03-01 Thread Heikki Linnakangas
Andy Lester wrote: > The following bug has been logged online: > > Bug reference: 5355 > Logged by: Andy Lester > Email address: a...@petdance.com > PostgreSQL version: 8.3.6 > Operating system: Linux > Description:locale incorrectly comma-separates "(null)" > Details:

Re: [BUGS] BUG #5356: citext not acting like case insensitive search

2010-03-01 Thread Tom Lane
"David E. Wheeler" writes: > Michael managed to fix this issue by moving citext to the "public" > schema. The question is, why would citext operators work in the public > schema but not when they're in some other schema? Is `=` resolving to > `TEXT = TEXT` if the "iss" schema isn't in the search p

Re: [BUGS] BUG #5356: citext not acting like case insensitive search

2010-03-01 Thread Tom Lane
"David E. Wheeler" writes: > Michael managed to fix this issue by moving citext to the "public" > schema. The question is, why would citext operators work in the public > schema but not when they're in some other schema? Are they in the search path? > Michael, does this work? > Select citystate

Re: [BUGS] BUG #4673: pl/PgSQL: Bug, when updating changed composite types.

2010-03-01 Thread Robert Haas
Just to save anyone else reading through these the time it took for me to figure this out, this was resubmitted as bug #5353, and Tom replied to that one. ...Robert 2010/2/26 Oleg Serov : > Hello!? anybody will fix this bug? Hey! > > On Mon, Feb 23, 2009 at 5:11 PM, Oleg wrote: >> >> The followi

Re: [BUGS] Bug in triggers

2010-03-01 Thread Robert Haas
It's not obvious whether this is the same as one of the various other problems you've complained about. If it isn't, an English description of what you think the problem is would probably improve your odds. See also: http://wiki.postgresql.org/wiki/Guide_to_reporting_problems ...Robert 2010/2/2

Re: [BUGS] BUG #5356: citext not acting like case insensitive search

2010-03-01 Thread David E. Wheeler
On Mar 1, 2010, at 9:15 AM, Michael Gould wrote: > > The following bug has been logged online: > > Bug reference: 5356 > Logged by: Michael Gould > Email address: mgo...@intermodalsoftwaresolutions.net > PostgreSQL version: 8.4.2 > Operating system: Windows 2008 R2 Server, W

[BUGS] BUG #5356: citext not acting like case insensitive search

2010-03-01 Thread Michael Gould
The following bug has been logged online: Bug reference: 5356 Logged by: Michael Gould Email address: mgo...@intermodalsoftwaresolutions.net PostgreSQL version: 8.4.2 Operating system: Windows 2008 R2 Server, Windows 7 x64 Description:citext not acting like case insen

[BUGS] BUG #5354: Type timestamptz doesn't allow to store time zone

2010-03-01 Thread Vitali
The following bug has been logged online: Bug reference: 5354 Logged by: Vitali Email address: vit...@lumensoftware.com PostgreSQL version: 8.1.x 8.2.x Operating system: Windows, Linux Description:Type timestamptz doesn't allow to store time zone Details: I have a t

[BUGS] BUG #5355: locale incorrectly comma-separates "(null)"

2010-03-01 Thread Andy Lester
The following bug has been logged online: Bug reference: 5355 Logged by: Andy Lester Email address: a...@petdance.com PostgreSQL version: 8.3.6 Operating system: Linux Description:locale incorrectly comma-separates "(null)" Details: In my .psqlrc I have the followin

Re: [BUGS] Bug in procedure When you modificate table

2010-03-01 Thread Tom Lane
Oleg Serov writes: > submitted as #5353 > 2010/2/26 Oleg Serov It is really not necessary to spam the list with duplicate submissions. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.pos

Re: [BUGS] BUG #5353: Bug in procedure When you modificate table

2010-03-01 Thread Tom Lane
"Oleg" writes: > Description:Bug in procedure When you modificate table The example works okay in HEAD (9.0alpha4). I doubt we'd risk back-patching the fix --- it was a bit invasive IIRC. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgre

Re: [BUGS] BUG #5352: Bug in PL/PgSQL "SELECT .. INTO" statement parser

2010-03-01 Thread Tom Lane
"Oleg" writes: > DECLARE >row_test1 test1%rowtype; >row_test2 test2%rowtype; > BEGIN >SELECT test1, chunk_id >FROM test1 JOIN test2 ON(chunk.id = test2.chunk_id) >LIMIT 1 >INTO row_test1, row_test2; > Will throw error: > ERROR: LIMIT #,# syntax is not supporte

Re: [BUGS] BUG #5352: Bug in PL/PgSQL "SELECT .. INTO" statement parser

2010-03-01 Thread Alex Hunsaker
On Mon, Mar 1, 2010 at 02:22, Oleg wrote: > CREATE OR REPLACE FUNCTION "bug" () RETURNS pg_catalog.void AS > $body$ > DECLARE >   row_test1 test1%rowtype; >   row_test2 test2%rowtype; > BEGIN >   SELECT test1, chunk_id >       FROM test1 JOIN test2 ON(chunk.id = test2.chunk_id) >       LIMIT 1 >  

Re: [BUGS] BUG #5338: PG_DUMP fails due to invalid adnum value

2010-03-01 Thread Robert Haas
On Fri, Feb 26, 2010 at 1:49 AM, Toni Helenius wrote: > I did supply it? As cvs-attachment. I'll attach it again with txt-extension. > I tried to reproduce this too with Windows XP 32-bit, Windows 2003 64-bit. > And I couldn't. Of course I didn't find a Windows 2008 64-bit like the > original s

Re: [BUGS]

2010-03-01 Thread Robert Haas
On Fri, Feb 26, 2010 at 7:12 PM, Administrator wrote: > Logged by: Michael Kopljan > email: ad...@navigator-info.com > PostgreSQL version: 8.4.2 > Operating system: Windows 2008 Server > Description: bug in string comparison > Details: > > -- Drop > DROP TABLE IF EXISTS "public"."test" ; > -- Defi

Re: [BUGS] Bug in procedure When you modificate table

2010-03-01 Thread Oleg Serov
submitted as #5353 2010/2/26 Oleg Serov > Hey, anybody will answer here? > > 2008/7/4 Oleg Serov > > SQL BUG CODE: >> BEGIN; >> SELECT version(); -- "PostgreSQL 8.3.3 on i686-redhat-linux-gnu, compiled >> by GCC gcc (GCC) 4.1.2 20070626 (Red Hat 4.1.2-14)" >> CREATE TYPE "buggy_enum_first" AS E

[BUGS] BUG #5353: Bug in procedure When you modificate table

2010-03-01 Thread Oleg
The following bug has been logged online: Bug reference: 5353 Logged by: Oleg Email address: sero...@gmail.com PostgreSQL version: any Operating system: any Description:Bug in procedure When you modificate table Details: CREATE TYPE "buggy_enum_first" AS ENUM ( 'bug

Re: [BUGS] Bug in PL/PgSQL "SELECT .. INTO" statement parser

2010-03-01 Thread Oleg Serov
Submitted as #*5352 bug.* 2010/2/26 Oleg Serov > Up. Anybody will answer on this bug report? > > > 2009/1/21 Oleg Serov > >> Sorry, but is not important, i forgot to remove original table name >> "chunk_ad", but is not affected to the bug.. >> >> 2009/1/21 Oleg Serov : >> > Here is an example:

[BUGS] BUG #5352: Bug in PL/PgSQL "SELECT .. INTO" statement parser

2010-03-01 Thread Oleg
The following bug has been logged online: Bug reference: 5352 Logged by: Oleg Email address: sero...@gmail.com PostgreSQL version: any Operating system: any Description:Bug in PL/PgSQL "SELECT .. INTO" statement parser Details: CREATE TABLE test2 ( id BIGINT,