-admin@postgresql.org
Subject: Re: [ADMIN] Error in creating the backend query
I wish that were the case.
I am running 8.3.7 built from the FreeBSD ports.
All insertions and updates to that table (or any others) are done
exclusively through that (or other) stored procedures.
We only use ad
PostgreSQL 8.3.7 running on FreeBSD.
The following query:
update tblksalerts
set cleartime = x_cleartime,
laststatusid = x_statusid,
lastreplytext = x_replytxt,
lasttesttime =
Benjamin Krajmalnik wrote:
update tblksalerts set cleartime = '2009-07-29 10:49:50'::TIMESTAMP,
laststatusid = 7::INTEGER, lastreplytext = '0'::VARCHAR, lasttesttime =
'2009-07-29 10:49:50'::TIMESTAMP, lasteventsource is NULL::VARCHAR,
lasteventid is NULL::INTEGER, replyval = 0::REAL, trend =
I tried it with both on and off, and it did not make a difference.
-Original Message-
From: Alvaro Herrera [mailto:alvhe...@commandprompt.com]
Sent: Wednesday, July 29, 2009 3:20 PM
To: Benjamin Krajmalnik
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Error in creating
Alvaro Herrera alvhe...@commandprompt.com writes:
Benjamin Krajmalnik wrote:
Please note the lasteventsource is null instead of lasteventsource =
null which is being generated when the value of x_eventsource is null.
Do you have transform_null_equals set?
Even if he did, that wouldn't affect
Benjamin Krajmalnik wrote:
I tried it with both on and off, and it did not make a difference.
Please show a complete example.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
--
Sent via
TO postgres;
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Wednesday, July 29, 2009 3:31 PM
To: Alvaro Herrera
Cc: Benjamin Krajmalnik; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Error in creating the backend query
Alvaro Herrera alvhe...@commandprompt.com
Benjamin Krajmalnik k...@illumen.com writes:
Below is the full stored procedure.
All I can do is repeat that plpgsql does not behave that way. It never
has AFAIR, and it most definitely doesn't in any version new enough to
recognize the COST option to CREATE FUNCTION (ie, 8.3 and up). In fact,
: Alvaro Herrera; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Error in creating the backend query
Benjamin Krajmalnik k...@illumen.com writes:
Below is the full stored procedure.
All I can do is repeat that plpgsql does not behave that way. It
never
has AFAIR, and it most definitely
Benjamin Krajmalnik k...@illumen.com writes:
So the plpgsql stored procedure is definitely the source.
If you want to convince me of that you need to provide a *self
contained* demonstration. An out-of-context procedure definition
isn't helpful because I can't test it.
10 matches
Mail list logo
