From: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Transition Tables doesn´t have OID |
Date: | 2018-12-01 17:22:22 |
Message-ID: | a357b49f-0219-2d15-eef1-3724fa302e2d@matrix.gatewaynet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 1/12/18 6:51 μ.μ., PegoraroF10 wrote:
> ok
> then, help me to find alternatives to it.
> As I sad, sometimes whe change our PK, so using OID would be a smart way to
> have a join between old and new transition tables and we would like to use
> transition tables because each statement is a lot faster than each row for
> auditing purposes.
Unique key with a sequence, which you'll have to leave alone.
>
> So, whats the alternative ? One trigger for each row just for changing PK
> values (will occur few times) and another trigger for each statement to do
> the logging ?
>
>
>
> --
> Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2018-12-01 18:37:52 | Re: Transition Tables doesn´t have OID |
Previous Message | Slavcho Trnkovski | 2018-12-01 16:56:06 | Re: postgis after pg_upgrade |