Re: [SQL] Strang behaviour SELECT ... LIMIT n FOR UPDATE

2007-11-27 Thread Bruce Momjian
Tom Lane wrote: > "Daniel Caune" <[EMAIL PROTECTED]> writes: > > I'm facing a strange behaviour with a statement SELECT ... LIMIT n FOR > > UPDATE in PostgreSQL 8.1. The number of rows returned is actually (n - > > 1). I'm trying to find whether this is an identified issue with > > PostgreSQL 8.1

Re: [SQL] Strang behaviour SELECT ... LIMIT n FOR UPDATE

2007-11-27 Thread Tom Lane
"Daniel Caune" <[EMAIL PROTECTED]> writes: > I'm facing a strange behaviour with a statement SELECT ... LIMIT n FOR > UPDATE in PostgreSQL 8.1. The number of rows returned is actually (n - > 1). I'm trying to find whether this is an identified issue with > PostgreSQL 8.1 that might have been fixe

Re: [SQL] NULLIF problem

2007-11-27 Thread Michael Glaesemann
On Nov 27, 2007, at 21:04 , Gera Mel Handumon wrote: I encounter an error if i use NULLIF with timestamp with time zone. eq. dbtime=nullif(mytime,'') i want to null the value of field DBTIME if the variable mytime=" " DBTIME ="timestamp with time zone" datatype error: column DBTIME is of typ

[SQL] NULLIF problem

2007-11-27 Thread Gera Mel Handumon
HELLO, I encounter an error if i use NULLIF with timestamp with time zone. eq. dbtime=nullif(mytime,'') i want to null the value of field DBTIME if the variable mytime=" " DBTIME ="timestamp with time zone" datatype error: column DBTIME is of type timestamp with time zone but expression is of t

[SQL] Strang behaviour SELECT ... LIMIT n FOR UPDATE

2007-11-27 Thread Daniel Caune
Hi, I'm facing a strange behaviour with a statement SELECT ... LIMIT n FOR UPDATE in PostgreSQL 8.1. The number of rows returned is actually (n - 1). I'm trying to find whether this is an identified issue with PostgreSQL 8.1 that might have been fixed in a later version such as 8.2; I don't have

Re: [SQL] pg_clog (?) problem with VACUMM

2007-11-27 Thread Stefan Becker
Dear Gerardo and Pgsql-List, >When executing a VACUUM, i have this msg: >gse_new_version=# VACUUM ; >ERROR: could not access status of transaction 118 >DETAIL: could not open file "pg_clog/": No existe el fichero o el I had a similar problem. I decided one day to "clean" out The pg_clog/ d

Re: [SQL] pg_clog (?) problem with VACUMM

2007-11-27 Thread Gerardo Herzig
Gregory Stark wrote: "Gerardo Herzig" <[EMAIL PROTECTED]> writes: Hi all. Well, im having this problem for the first time. When executing a VACUUM, i have this msg: gse_new_version=# VACUUM ; ERROR: could not access status of transaction 118 DETAIL: could not open file "pg_clog/": No

Re: [SQL] pg_clog (?) problem with VACUMM

2007-11-27 Thread Gregory Stark
"Gerardo Herzig" <[EMAIL PROTECTED]> writes: > Hi all. Well, im having this problem for the first time. > When executing a VACUUM, i have this msg: > gse_new_version=# VACUUM ; > ERROR: could not access status of transaction 118 > DETAIL: could not open file "pg_clog/": No existe el fichero

[SQL] pg_clog (?) problem with VACUMM

2007-11-27 Thread Gerardo Herzig
Hi all. Well, im having this problem for the first time. When executing a VACUUM, i have this msg: gse_new_version=# VACUUM ; ERROR: could not access status of transaction 118 DETAIL: could not open file "pg_clog/": No existe el fichero o el directorio Ok, wtf, i will create the file. So