e the trigger itself, the
trigger procedure must be created like this:
CREATE OR REPLACE FUNCTION test() RETURNS trigger AS $BODY$
my ($a, $b) = @{$_TD->{args}}; # $a and/or $b may be null, depending
on how CREATE TRIGGER was used
...
I hope someone finds that helpful,
Kev
--
Sent
sage').
I don't understand the rationale for this limitation. It seems to
make inheritance much less useful, because then (very frequently used)
SELECT, UPDATE, etc. statements have the extra (programming and
execution) overhead of at least one SET ROLE statement, and worse,
probab
I went to upgrade an installation and was stopped with (approximately)
the following message after clicking Next on the step where I told it
to use the same data directory:
"The existing data directory (date time: floating-point numbers) is
not compatible with this server (date time: 64-bit intege
ext with a known one? Doesn't this seem inconsistent? If it
does seem inconsistent, should I be careful how to code because this
might change in the future?
Thanks,
Kev
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
at point the 'old' is missing,
before the case even gets to be parsed. How do I get around this
without having two 'perform' statements? Is there no short-circuit
option in plpgsql?
Thanks,
Kev
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ly difference
was whether I was on Terminal Services or not. Running TS using
"mstsc.exe /console" (even within a session) worked for me.
Peace,
Kev
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Apr 8, 11:08 am, [EMAIL PROTECTED] (Alvaro Herrera) wrote:
> Kev escribió:
>
> > > Recompile PG? Even if I'm running 8.3.1, released well after that?
>
> > Oh, sorry, do you mean, it's ready for 5.10 but still compiled with
> > 5.8 for now? If so, is
On Apr 8, 11:48 am, [EMAIL PROTECTED] (Richard Huxton) wrote:
> Kev wrote:
> >> Recompile PG? Even if I'm running 8.3.1, released well after that?
>
> > Oh, sorry, do you mean, it's ready for 5.10 but still compiled with
> > 5.8 for now? If so, is there
> Recompile PG? Even if I'm running 8.3.1, released well after that?
>
> Thanks,
> Kev
Oh, sorry, do you mean, it's ready for 5.10 but still compiled with
5.8 for now? If so, is there a timeline for compiling with 5.10 by
default in the production releases of pgsql?
Tha
On Apr 7, 10:37 am, [EMAIL PROTECTED] (Tom Lane) wrote:
> Kev <[EMAIL PROTECTED]> writes:
> > I'm trying to upgrade to perl 5.10, and realized that plperlu is still
> > using 5.8. How exactly does pgsql determine where to look/what
> > version to use for plperlu?
or die("Couldn't execute statement: " . $sth-
>diestr);
local our @data;
while (@data = $sth->fetchrow_array())
{
$r->print("Killing $data[0]...");
system('"c:\program files\postgresql\8.3\bin\pg_ctl.exe" kill TERM
' . $data[0]) ==
I'm trying to upgrade to perl 5.10, and realized that plperlu is still
using 5.8. How exactly does pgsql determine where to look/what
version to use for plperlu?
Thanks,
Kev
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
On Apr 6, 1:34 pm, [EMAIL PROTECTED] (Craig Ringer) wrote:
> Kev wrote:
> > So I tried to do this in Perl, but for some reason neither
> > kill() nor Win32::Process::KillProcess() actually terminate the
> > threads.
>
> Threads? Each backend is a distinct process. I have
s mean I have to run a separate database server for each
database just to be able to boot people off a particular database
before dropping it? It seems like a basic thing to be able to drop a
database unconditionally without restarting the service for people who
are using other databases on the same se
ecome INSERT INTO persons
VALUES (?, ?) and then you would pass the execution function your two
values and it would escape them properly for you. At least that's how
it works with Perl and DBI.
Kev
---(end of broadcast)---
TIP 9: In versions b
he quote_ident() function in the docs, you'll likely need
that for both cases.
Kev
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
e?
Er...I guess the web server would then be the cap? Or whatever other
tiers you had between the client and pgsql?
Kev
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
On Apr 19, 9:41 am, Kev <[EMAIL PROTECTED]> wrote:
> On Apr 17, 10:27 am, [EMAIL PROTECTED] (Mageshwaran) wrote:
>
> > hi everyone,
>
> > please any one give any methods to do incremental backups. it is urgent
> > .. help me
>
> > Regards
> >
esh start' backup where you take all audit
entries. There's another thread starting about audit trails, you
might want to check there.
Kev
---(end of broadcast)---
TIP 6: explain analyze is your friend
I can jump on a
neighbouring computer and start creating tables and such. Very cool!
Still not sure why my home PC doesn't like it though...
Kev
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
da Project on pg_live?
Thanks,
Kev
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Mar 27, 10:34 am, [EMAIL PROTECTED] (Aidan Van Dyk) wrote:
>
> Sounds something like mod_libpq:
>http://asmith.id.au/mod_libpq.html
Thanks, I appreciate the link...also looks promising.
Kev
---(end of broadcast)---
TIP 6: explai
> > Or SQL-on-rails
> > http://www.sqlonrails.org/
>
> LOL!
>
> merlin
Heh heh..."insufficiently AJAX-y"
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PR
l server
itself
publicly accessible on some port. Is that just asking for trouble?
I appreciate any comments or thoughts anyone might have on this.
Thanks,
Kev
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
Hi everyone,
I heard Firebird has database-wide triggers, and I've seen mention of
them on this newsgroup here and there. Is that on the map for
implementation in pgsql?
Thanks,
Kev
---(end of broadcast)---
TIP 3: Have you checked our exte
Sorry...are you asking something or sharing what works well for a
certain purpose?
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
26 matches
Mail list logo