On 15/10/2023 10:59 pm, Tom Lane wrote:
Konstantin Knizhnik writes:
One our customer complains that he spawned two `create index
concurrently` for two different tables and both stuck in"waiting for old
snapshots".
I wonder if two CIC can really block each other in `WaitForOlderSnapshots`?
Si
Konstantin Knizhnik writes:
> One our customer complains that he spawned two `create index
> concurrently` for two different tables and both stuck in"waiting for old
> snapshots".
> I wonder if two CIC can really block each other in `WaitForOlderSnapshots`?
Since v14, we won't wait for another
I noticed this on PG 10 recently, while I agree it is an obsolete version.
pg_blocking_pids() showed that one of the CIC on a Table is blocked
by a CIC on another Table.
I saw them both created over a period of time after which I doubted
what was reported by pg_blocking_pids().
As it was PG 10, I
One our customer complains that he spawned two `create index
concurrently` for two different tables and both stuck in"waiting for old
snapshots".
I wonder if two CIC can really block each other in `WaitForOlderSnapshots`?
I found the similar question in hacker archive:
https://www.postgresql.or