| From: | Fabrice Chapuis <fabrice636861(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: wrong sequence value in dump file |
| Date: | 2025-07-16 15:25:21 |
| Message-ID: | CAA5-nLCP6C=5v4JX0xV5L+2cT6d6BJqg0u0uU=VH_2yv12R3vg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Ok, effectively the dump comes from a standby. Thanks for your explanation.
Best regards,
Fabrice
On Wed, Jul 16, 2025 at 5:06 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Fabrice Chapuis <fabrice636861(at)gmail(dot)com> writes:
> > When dumping with pg_dump and the directory option, I got a sequence
> value
> > that is greater in the dump file than the sequence in the source
> database.
>
> Perhaps you were dumping from a standby server? It's normal for
> a standby to show a value up to 32 counts more than the primary,
> because of some tricks that sequence.c plays to reduce the number
> of WAL records generated for nextval().
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yura Sokolov | 2025-07-16 15:27:45 | Re: Read-Write optimistic lock (Re: sinvaladt.c: remove msgnumLock, use atomic operations on maxMsgNum) |
| Previous Message | Jacob Champion | 2025-07-16 15:24:17 | Re: Explicitly enable meson features in CI |