From: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
---|---|
To: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Issue with logical replication: MyPgXact->xmin already is valid |
Date: | 2017-10-06 12:29:17 |
Message-ID: | 91a97dc3-1981-7d0b-f1f5-8a767e516bff@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 06/10/17 12:16, Konstantin Knizhnik wrote:
> When creating logical replication slots we quite often get the following
> error:
>
> ERROR: cannot build an initial slot snapshot when MyPgXact->xmin
> already is valid
>
> which cause restart of WAL sender.
> The comment to this line doesn't clarify much:
>
> /* so we don't overwrite the existing value */
> if (TransactionIdIsValid(MyPgXact->xmin))
> elog(ERROR, "cannot build an initial slot snapshot when
> MyPgXact->xmin already is valid");
>>
> I wonder if it is normal situation or something goes wrong?
>
Hi,
no it's not normal situation, it seems you are doing something that
assigns xid before you run the CREATE_REPLICATION_SLOT command on that
connection.
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Kuzmenkov | 2017-10-06 12:38:52 | Re: Proposal: Improve bitmap costing for lossy pages |
Previous Message | Andrey Borodin | 2017-10-06 12:25:16 | On markers of changed data |