>> On Sat, Apr 30, 2016 at 1:38 AM, wrote:
>> > I have a table with a row update trigger that is quite slow.
>> > The trigger finction basically sets some bits in a "changed" column
>> > depending on which values really changed.
>> > For some bulk updates it can be determined in advance that the
>> On 2016-04-30 02:08, wolfg...@alle-noten.de wrote:
>> > Hi,
>> >
>> > I have a table with a row update trigger that is quite slow.
>> > The trigger finction basically sets some bits in a "changed" column
>> > depending on which values really changed.
>> > For some bulk updates it can be determi
On 2016-04-30 02:08, wolfg...@alle-noten.de wrote:
> Hi,
>
> I have a table with a row update trigger that is quite slow.
> The trigger finction basically sets some bits in a "changed" column
> depending on which values really changed.
> For some bulk updates it can be determined in advance that t
On Sat, Apr 30, 2016 at 1:38 AM, wrote:
> I have a table with a row update trigger that is quite slow.
> The trigger finction basically sets some bits in a "changed" column
> depending on which values really changed.
> For some bulk updates it can be determined in advance that the
> trigger funct
If your other inserts can wait you could maybe combine DISABLE TRIGGER
with LOCK TABLE?
http://www.postgresql.org/docs/current/static/sql-lock.html
Someone else may know a better solution...
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscript
Hi,
I have a table with a row update trigger that is quite slow.
The trigger finction basically sets some bits in a "changed" column
depending on which values really changed.
For some bulk updates it can be determined in advance that the
trigger function will not have any effect.
Is there any way
