| From: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: xmin increasing within a transaction block? |
| Date: | 2017-11-06 13:59:52 |
| Message-ID: | CAKoxK+5XZfmBFTBxxGQB+bAeio24h5zyV6-in5322Y_zeQkpVg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Nov 6, 2017 at 1:53 PM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> Something is using subtransactions there. My first guess would be that
> there are triggers with EXCEPTION blocks, but your example doesn't show
> any. Or maybe you have event triggers.
Thanks, but I don't see any event trigger:
> \dy
List of event triggers
Name | Event | Owner | Enabled | Procedure | Tags
------+-------+-------+---------+-----------+------
(0 rows)
Please note that I tested it on a freshly created database obtaining
the same behavior.
I did have in the past event trigger, but I have dropped long time
before this behavior.
Any other idea?
Luca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luca Ferrari | 2017-11-06 14:05:07 | Re: xmin increasing within a transaction block? |
| Previous Message | Sachin Kotwal | 2017-11-06 13:33:08 | Re: Naming conventions for column names |