| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Autovaccuum vs temp tables crash |
| Date: | 2019-02-26 23:26:32 |
| Message-ID: | 20190226232632.GA13885@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Feb-23, Tom Lane wrote:
> However, if someone held a gun to my head and said fix it, I'd be inclined
> to do so by having temp-namespace creation insert a "pin" dependency into
> pg_depend. Arguably, the only reason we don't create all the temp
> namespaces during bootstrap is because we aren't sure how many we'd need
> --- but if we did do that, they'd presumably end up pinned.
Is there a problem if we start with very high max_backends and this pins
a few thousands schemas that are later no longer needed? There's no
decent way to drop them ... (I'm not sure it matters all that much,
except for bloat in pg_namespace.)
How about hardcoding a pin for any schema that's within the current
max_backends?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-02-26 23:29:37 | Re: Index INCLUDE vs. Bitmap Index Scan |
| Previous Message | Benjamin Manes | 2019-02-26 23:23:57 | Re: [Patch][WiP] Tweaked LRU for shared buffers |