Re: [BUGS] wrong timezone precision using plpythonu trigger

2010-10-10 Thread Tom Lane
maizi writes: > CREATE LANGUAGE plpythonu ; > CREATE FUNCTION wrong() RETURNS trigger AS $wrong$ > from mx import DateTime > TD['new']['modif_time'] = DateTime.now() > return 'MODIFY' > $wrong$ LANGUAGE plpythonu; > CREATE TABLE pb ( a TEXT, modif_time TIMESTAMP(0) WITHOUT TIME ZONE ) ; > CREA

Re: [BUGS] BUG #5702: pg fails to use a conditional index even the where clause matches the condition

2010-10-10 Thread Tom Lane
Jeff Davis writes: > On Sat, 2010-10-09 at 23:28 +, Corin wrote: >> I'd consider this a bug as "NOT x IS NULL" is the same as "x IS NOT NULL". > That is false. It's true for scalar input datatypes, though. I had been wary of this idea because I didn't see any suitably cheap place to insert

Re: [BUGS] BUG #5699: Postgres runs only under default user.

2010-10-10 Thread Craig Ringer
On 10/08/2010 07:53 PM, Johannes Meidert wrote: The following bug has been logged online: Bug reference: 5699 Logged by: Johannes Meidert Email address: johannes.meid...@rohde-schwarz.com PostgreSQL version: 9.0.1 Operating system: windows Description:Postgres runs

[BUGS] wrong timezone precision using plpythonu trigger

2010-10-10 Thread maizi
Hello, I am using some code since postgres 8 and testing it on postgresql 9. Here are the informations about the packages and system used: # lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux unstable (sid) Release:unstable Codename:

[BUGS] rollback to savepoint leads to transaction already in progress

2010-10-10 Thread David Newall
Hi all, Trivial program to demonstrate problem: main() { ECPGdebug(1,stderr); exec sql connect to postgres; exec sql set autocommit to off; exec sql start transaction; exec sql savepoint s; exec sql rollback to s; exec sql commit; return 0; } Output: [28397]: E

Re: [BUGS] BUG #5702: pg fails to use a conditional index even the where clause matches the condition

2010-10-10 Thread Jeff Davis
On Sat, 2010-10-09 at 23:28 +, Corin wrote: > I'd consider this a bug as "NOT x IS NULL" is the same as "x IS NOT NULL". That is false. http://thoughts.j-davis.com/2009/08/02/what-is-the-deal-with-nulls/ "NOT x IS NULL is not the same as x IS NOT NULL — If x is ROW(1,NULL), then the former w

Re: [BUGS] BUG #5702: pg fails to use a conditional index even the where clause matches the condition

2010-10-10 Thread Netskin | Corin Langosch
On 10.10.2010 05:26, Tom Lane wrote: Try it like WHERE amazon_product_id IS NOT NULL; You are right. When I change the condition on the index like this, the index gets used as it should. Even without having to specify the extra not null condition in the query. We don't expend an i