>> On 2016-07-09 08:20, haman...@t-online.de wrote:
>> > Hi,
>> >
>> > a table is associated with a trigger for normal use.
>> > An admin (someone with ALTER privilege) can disable tthe trigger, run some
>> > bulk update,
>> > and then re-enable it. This means, however, that normal user
>> On 2016-07-09 08:20, haman...@t-online.de wrote:
>> > Hi,
>> >
>> > a table is associated with a trigger for normal use.
>> > An admin (someone with ALTER privilege) can disable tthe trigger, run some
>> > bulk update,
>> > and then re-enable it. This means, however, that normal user
On 2016-07-09 08:20, haman...@t-online.de wrote:
Hi,
a table is associated with a trigger for normal use.
An admin (someone with ALTER privilege) can disable tthe trigger, run some bulk
update,
and then re-enable it. This means, however, that normal user activity has to
be locked out.
There
haman...@t-online.de wrote:
Hi,
a table is associated with a trigger for normal use.
An admin (someone with ALTER privilege) can disable tthe trigger, run some bulk
update,
and then re-enable it. This means, however, that normal user activity has to
be locked out.
There are two possible
Good morning
> -Original Message-
> From: pgsql-general-ow...@postgresql.org
> [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of hamann.w@t-
> online.de
> Sent: Samstag, 9. Juli 2016 08:20
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] Running
Hi,
a table is associated with a trigger for normal use.
An admin (someone with ALTER privilege) can disable tthe trigger, run some bulk
update,
and then re-enable it. This means, however, that normal user activity has to
be locked out.
There are two possible scenarios: the bulk update would
