On Friday, June 7, 2024, Bernd Eckenfels wrote:
>
>
> As a user I want to know if CLUSTERing also frees space, and since it
> has the effect of doing so (and not pre-allocates, which is a bit odd),why
> not mention it.
>
Yeah, it doesn’t make it clear that rewriting the table means that only
live
I am mostly „hung up“ on extending the doc to make it even more
usedul (by sharing my use cases).
As a user I want to know if CLUSTERing also frees space, and since it
has the effect of doing so (and not pre-allocates, which is a bit odd),why
not mention it.
Btw where is that friendly community t
Hello,
David G. Johnston wrote on 7. June 2024 15:24 (GMT +02:00):
> All of that is already covered on the page.
You are right, I missed the note about the two modes and their storage
consumption, I guess that part is described enough
> If you think it needs
> rewording I suggest you specify exa
On Fri, Jun 7, 2024, 10:57 Bernd Eckenfels wrote:
>
> Is the following correct (I.e. it does not preserv free pages) and can
> be added?
>
You are hung up on the idea of free pages when this operation makes them
irrelevant. Complete new files are written, populated to the extent of
fill factor,
On Thursday, June 6, 2024, PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/16/sql-cluster.html
> Description:
>
> The cloister command should describe how or deals with free pages (I.e. are
> released) and
I just noticed, it does describe that it takes an exclusive access lock, so that part is covered. (Maybe add „This is not an „ONLINE“ operation“ as this use a more common terminology?)
Thanks for your workBernd
Von: PG Doc comments form Gesendet: Freitag, Juni 7, 2024 5:
