| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | James Coleman <jtc331(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, "Bossart, Nathan" <bossartn(at)amazon(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Document atthasmissing default optimization avoids verification table scan |
| Date: | 2022-03-25 21:00:43 |
| Message-ID: | 3465237.1648242043@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I vote for rejecting both of these patches.
I see what James is on about here, but I agree that these specific changes
don't help much. What would actually be desirable IMO is a separate
section somewhere explaining the performance characteristics of ALTER
TABLE. (We've also kicked around the idea of EXPLAIN for ALTER TABLE,
but that's a lot more work.) This could coalesce the parenthetical
remarks that exist in ddl.sgml as well as alter_table.sgml into
something a bit more unified and perhaps easier to follow. In particular,
it should start by defining what we mean by "table rewrite" and "table
scan". I don't recall at the moment whether we define those in multiple
places or not at all, but as things stand any such discussion would be
pretty fragmented.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2022-03-25 21:01:01 | Re: SSL/TLS instead of SSL in docs |
| Previous Message | Thomas Munro | 2022-03-25 20:55:47 | Re: pgsql: Add 'basebackup_to_shell' contrib module. |