c
> case where i need it. Can it be done?
>
AFAIK Locking the entire database may not be an option in postgresql.
However you can virtually restrict access to everyone to a particular
database via pg_hba.conf.
More details here
http://www.postgresql.org/docs/8.2/static/auth-pg-hba-conf
-
> TIP 2: Don't 'kill -9' the postmaster
>
AFAIK the FOUND variable does not get updated as part of an EXECUTE command.
Consider using a strict INTO clause alongwith EXECUTE. This way a
NO_DATA_FOUND exception will be generated if your query did'nt return any
data. Something like this:
DECLARE
v_rec record;
BEGIN
EXECUTE ''SELECT * FROM '' || TG_RELNAME || '' WHERE fldclientnumber = '' ||
NEW.fldclientnumber INTO STRICT v_rec;
EXCEPTION
when no_data_found then
/* do something */
regards,
--
Sibte Abbas
-- Forwarded message --
From: Sibte Abbas <[EMAIL PROTECTED]>
Date: Aug 31, 2007 8:32 AM
Subject: Re: [GENERAL] Query the catalog
To: Ottó Havasvölgyi <[EMAIL PROTECTED]>
On 8/31/07, Ottó Havasvölgyi <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> How can I q
On 8/25/07, Thobiyas <[EMAIL PROTECTED]> wrote:
> Dear sir
> how can get the log file in postgres sql
>
> --
> **
> P.Maria Antony Thobiyas
> Bosco InfoTech Pvt Ltd
>
> Mobile: 09486144070 (Personal)
> ***
On 8/3/07, Sergey Moroz <[EMAIL PROTECTED]> wrote:
> No that is not I meant. The problem in Prepared statements is in that you
> should determine SQL inside the function. I want to pass a query as a
> parameter, as well as query parameters.
> For example (I want to create a function like the follow
On 8/2/07, Sergey Moroz <[EMAIL PROTECTED]> wrote:
> The problem is that I can't find the way to exclude query parsing (prepare
> step) for custom queries. In other words I want to create a function that
> accepts a query text with "$1, $2, etc." and variables as params, executes
> the query and re
tters/2007-07/msg00215.php
Makes sense.
regards,
--
Sibte Abbas
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
On 7/22/07, Sibte Abbas <[EMAIL PROTECTED]> wrote:
On 7/22/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> Shreya Bhargava <[EMAIL PROTECTED]> writes:
> > 1. gdb postgres
> > 2. set args -D test (test is my dbcluster)
> > 3. b hashbuild(this is the function i
exec gdb $PGINSTROOT/bin/postgres -silent
fi
This will attach directly to the target backend if there's only one,
else you can examine the ps output to determine which PID to attach to.
regards, tom lane
Also, for gdb to function properly, you should compile the s
_server_log() function in elog.c?
thanks,
--
Sibte Abbas
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
ROTECTED] ~]$ psql --version
psql (PostgreSQL) 7.4.8
contains support for command-line editing
thx.
This can happen when your index is/are corrupted. Try issuing a
reindex command.
regards,
--
Sibte Abbas
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
Thx for help.
Noah
Are you trying to do this from a plpgsql function? If so then I think
you should try to do this from a C function.
With C functions you will get more control over the new and old
versions of the tuple since you get their pointers via
TriggerData->tg_trigtuple (old tuple)
12 matches
Mail list logo