> Le 20/07/09 15:19, chester c young a écrit :
> > within a trigger need to know if the UPDATE statement
> set a column. the column might be set to the old value
> or a different value.
> >
> > (want to make sure the app is sending all necessary
> values)
> >
> > thanks
> >
>
> If the column
Rob Sargent writes:
> The ascii dump has serveral CREATE FUNCTION gbtreeN_{in,out} but I don't
> see them in the current (source) database using '\df gbtree*'.
Which ones? Pre-8.4 \df will deliberately suppress I/O functions
(or functions that it thinks are I/O functions, anyway).
The ascii dump has serveral CREATE FUNCTION gbtreeN_{in,out} but I don't
see them in the current (source) database using '\df gbtree*'. Using
'\df gbt*' I get 111 functions for which all the names begin 'gbt_'.
Have I lost them? The gbtreekeyN types are still there.
Tom Lane wrote:
Rob Sar
Wonderful news.
I just ran dump and restore against same production server. Constraints
and the absence of drop calls appears to have saved my butt.
Tom Lane wrote:
Rob Sargent writes:
Is there a difference in the order of execution between an ascii dump
and one using the "custom" fo
Rob Sargent writes:
> Is there a difference in the order of execution between an ascii dump
> and one using the "custom" format? Or any difference in the general
> operation?
There's not supposed to be. One standard test on the pg_dump code is
pg_dump >textfile
pg_dump -Fc >d
Is there a difference in the order of execution between an ascii dump
and one using the "custom" format? Or any difference in the general
operation?
I need to know if I can rely on the ascii version to tell me what the
custom format might have done.
--
Sent via pgsql-sql mailing list (pgs
Hello,
On 20/07/09 21:59, JJ wrote :
> [...]
> I want to sort and query the database based on the
> hex addresses [...]
> How can I store hex values in PostgreSQL and sort and query them?
>
PostgreSQL (since version 8.3 and maybe older) sets string functions for
encoding/decoding strings from/t
