Hi all,
Thanks to those on this list who contribute their knowledge for our
consumption! I have another question:
The problem I'm having is in one particular spot where I'm trying to run a
parametized query inside a PL/PgSQL function. When I run the query directly,
the planner correctly
!
From: Tom Lane [EMAIL PROTECTED]
Sent: Tuesday, December 18, 2007 10:11 AM
To: Weber, Geoffrey M.
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Problem with index not being chosen inside PL/PgSQL
function...
Weber, Geoffrey M. [EMAIL PROTECTED
PROTECTED]
Sent: Tuesday, December 18, 2007 10:36 AM
To: Weber, Geoffrey M.
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Problem with index not being chosen inside PL/PgSQL
function...
Weber, Geoffrey M. [EMAIL PROTECTED] writes:
Hmm - good question! However, it is - both the id
, Geoffrey M.
Cc: Tom Lane; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Problem with index not being chosen inside PL/PgSQL
function...
On Dec 18, 2007 10:54 AM, Weber, Geoffrey M.
[EMAIL PROTECTED] wrote:
Tom,
Yes, the distribution must be what's doing it. I guess I knew
I've been trying for quite a while to get Postgresql tuned for use as an
OLTP system. I have several PL/pgSQL functions that handle inserts and
updates to the main table and several near-real-time daemons written that
access the data and can take automated actions on it (email/page concerned
I'm having a problem, and can't seem to find a good answer in the mailing
list archives... sorry if I'm missing something obvious!
Postgres version: 8.2.4
O/S: Solaris 10
I want to set a BOOLEAN column value to FALSE by default for all INSERT and
UPDATE statements performed against a particular
