Re: Postgres is not able to handle more than 4k tables!? - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: Postgres is not able to handle more than 4k tables!?
Date
Msg-id CAPpHfdv4tjxwiyrPSEE=T=oc3HN62xPa9YEVjX=_70Kpb1ZJuw@mail.gmail.com
Whole thread Raw
In response to Re: Postgres is not able to handle more than 4k tables!?  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Responses Re: Postgres is not able to handle more than 4k tables!?
List pgsql-hackers
On Thu, Jul 9, 2020 at 6:57 PM Konstantin Knizhnik
<k.knizhnik@postgrespro.ru> wrote:
> 2. Remember in relation info XID of oldest active transaction at the
> moment of last autovacuum.
> At next autovacuum iteration we first of all compare this stored XID
> with current oldest active transaction XID
> and bypass vacuuming this relation if XID is not changed.


This option looks good for me independently of the use case under
consideration.  Long-running transactions are an old and well-known
problem.  If we can skip some useless work here, let's do this.

------
Regards,
Alexander Korotkov



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Stale external URL in doc?
Next
From: Stephen Frost
Date:
Subject: Re: Postgres is not able to handle more than 4k tables!?