I havn't been able to find documentation on how to use \d. When I open the
psql interface (through either port ) it asks for a password but doesn't
allow any entry of a password.
However, after my last e-mail to you, I came across something interesting -
at least to me.
I use pg_admin scripts to modify triggers.
Looking through pg_admin at all of the triggers on the p_id.processes table
I just happened to click on the trigger we have been discussing and then
clicked its refresh button.
Using the same update statement and the same After Update trigger that
inserted two rows into p_id.devices it now inserted only one row and that
row was the correct row.
I don't know enough about the interaction between the unrefreshed copy of a
trigger held by pg_admin and the updated trigger installed in the server to
comment - however there does seem to be a connection of which I wasn't
aware.
Bob
----- Original Message -----
From: "Adrian Klaver" <adrian.klaver@xxxxxxxxx>
To: "Bob Pawley" <rjpawley@xxxxxxx>
Cc: "Tom Lane" <tgl@xxxxxxxxxxxxx>; "Postgresql"
<pgsql-general@xxxxxxxxxxxxxx>
Sent: Friday, January 22, 2010 3:37 PM
Subject: Re: Old/New
On Friday 22 January 2010 3:25:34 pm Bob Pawley wrote:
No
The table p_id.processes is the start of the fluid_id ident and that
column
is serial.
Bob
Per Tom's suggestion can we see \d for p_id.processes and for good measure
p_id.devices ?
--
Adrian Klaver
adrian.klaver@xxxxxxxxx
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
