| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, "tgl(at)sss(dot)pgh(dot)pa(dot)us" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "robertmhaas(at)gmail(dot)com" <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Temporary tables prevent autovacuum, leading to XID wraparound |
| Date: | 2018-08-09 07:00:29 |
| Message-ID: | 20180809070029.GF13638@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 09, 2018 at 08:32:32AM +0530, Andres Freund wrote:
> My point is that the documentation isn't sufficient. Not that there's an active problem.
OK. Attached is the latest version if the patch I have that I was
preparing for commit.
On top of isTempNamespaceInUse I have this note:
+ * Note: this can be used while scanning relations in pg_class to detect
+ * orphaned temporary tables or namespaces with a backend connected to a
+ * given database.
Would you be fine if I add an extra note like what's in
BackendIdGetProc? Say "The result may be out of date quickly, so the
caller must be careful how to handle this information."
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Make-autovacuum-more-aggressive-to-remove-orphaned-t.patch | text/x-diff | 9.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuro Yamada | 2018-08-09 07:22:38 | Typo in optimizer/README |
| Previous Message | Peter Geoghegan | 2018-08-09 05:08:26 | Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes |