| From: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: xmin increasing within a transaction block? |
| Date: | 2017-11-06 14:05:07 |
| Message-ID: | CAKoxK+66F7BQZXh=_ZM2nfZ_V1oD7K64z1fKMdguBqYShC0m2Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Nov 6, 2017 at 2:29 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> That doesn't look like plain postgres behaviour to me. Any chance you're
> using a pooler in statement mode in front of postgres?
None I'm aware of, since the machine is using postgresql locally and
I'm connecting to it using the port 5432.
I did have in the past enabled wal_level to logical but now it is set
to minimal and I don't have any replication slot (in the case it could
do something related to this behvior):
# SELECT * FROM pg_replication_slots;
(0 rows)
Any idea?
Luca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-11-06 14:10:23 | Re: xmin increasing within a transaction block? |
| Previous Message | Luca Ferrari | 2017-11-06 13:59:52 | Re: xmin increasing within a transaction block? |