| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Vladimir Borodin <root(at)simply(dot)name>, Oleksii Kliukin <alexk(at)hintbits(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [ADMIN] Replication slots and isolation levels |
| Date: | 2015-11-03 08:38:42 |
| Message-ID: | 20151103083842.GQ11897@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
On 2015-11-02 15:37:57 -0500, Robert Haas wrote:
> On Fri, Oct 30, 2015 at 9:49 AM, Vladimir Borodin <root(at)simply(dot)name> wrote:
> > I’ve tried two ways - bare SELECT in autocommit mode and BEGIN; SELECT;
> > ROLLBACK. I first described the problem in thread on pgsql-admin@ [0], there
> > is copy-paste from psql there, but during conversation initial description
> > was lost.
> >
> > [0]
> > http://www.postgresql.org/message-id/7F74C5EA-6741-44FC-B6C6-E96F18D761FB@simply.name
>
> Hmm. That behavior seems unexpected to me, but I might be missing something.
The conflict is because of a relation lock, not because of
visibility. Hot-Standby feedback changes nothing about that.
I presume all the other conflicts are all because of relation level
locks? Check pg_stat_database_conflicts and the server logs to verify.
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Borodin | 2015-11-03 09:51:22 | Re: [ADMIN] Replication slots and isolation levels |
| Previous Message | Vladimir Borodin | 2015-11-03 06:57:52 | Re: [HACKERS] Replication slots and isolation levels |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2015-11-03 08:41:39 | Re: pglogical_output - a general purpose logical decoding output plugin |
| Previous Message | Andres Freund | 2015-11-03 08:35:37 | Re: NOTIFY in Background Worker |