Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
However, I don't think we can promise never to change the ondisk
representation of data, nor the page layout. Sometimes an inplace
upgrade just won't work, ISTM.
We have talked about batching on-disk changes so that they'd only occur
Hello,
I want to create a trigger in PostgresSQL
In trigger, Before inserting the record, if
data is already in the table, the trigger fire the mesaage that data is already
there, and after that trigger ckeck for next insert statement.
Pleae help me in this
regard,kindly
reply.
Regards,
Andreas Pflug wrote:
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
However, I don't think we can promise never to change the ondisk
representation of data, nor the page layout. Sometimes an inplace
upgrade just won't work, ISTM.
We have talked about batching on-disk changes
Hello,I´m don´t if I´m sendind the question to the right list, but here it is.I want to know if I can use the following function on PostgreSQL 7.3.x.:dblink_connect(text,text)dblink_disconnect(text)I´m tried to use it on PostgreSQL 7.3.4 and it´s works well
Alvaro Herrera wrote:
Is anybody working or considering to work on pg_upgrade, or is all this
hypothetical? Our past history has seen lots of people offering to work
on pg_upgrade, and none has produced a working version. Is it fair or
useful to impose restrictions on development just because
On Fri, 2005-11-18 at 00:15 +, Simon Riggs wrote:
Minor comment update.
Applied with adjustments.
BTW, I noticed the following comment a few lines down in execMain.c
(circa line 1564):
* note: we can't run UPDATE queries with transactions
* off because UPDATEs are actually INSERTs and
i would like to unsubscribe my email... how will i do it?
Yahoo! FareChase - Search multiple travel sites in one click.
Neil Conway [EMAIL PROTECTED] writes:
BTW, I noticed the following comment a few lines down in execMain.c
(circa line 1564):
* note: we can't run UPDATE queries with transactions
* off because UPDATEs are actually INSERTs and our
* scan will mistakenly loop forever, updating the tuple
*
Andrew Dunstan [EMAIL PROTECTED] writes:
I will apply the attached patch tomorrow, barring objection. This covers
drop if exists for the following objects:
table view index sequence schema type domain conversion
I have a simple test script as show below, but I am not sure where to
put it
Alvaro Herrera [EMAIL PROTECTED] writes:
/*
! * Called to execute the utility commands GRANT and REVOKE.
! *
! * stmt may be a complete GrantStmt created by the parser, or it may be
! * missing the objects list and the grantees list. In this case,
! * they are taken from the second
10 matches
Mail list logo