Re: Column Tetris Automatisation

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Nicolas Paris <niparisco(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Column Tetris Automatisation
Date: 2017-01-15 10:01:57
Message-ID: CAFj8pRAADRiHuSpL11KQsd27mz059hk05a_vhNpJFO+0OzM+UA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi

2017-01-15 10:58 GMT+01:00 Nicolas Paris <niparisco(at)gmail(dot)com>:

> Hello,
>
> In postgresl order of columns does have an non negligeable impact on table
> size[1].
> Table are in many cases dynamic, and new fields can appear in the database
> life.
> I suspect re-ordering columns based on types would be an automatisable
> task would be feaseable such:
>
> ```
> reorderTableWithTetrisAlgo(table)
> return reordered_table
> ```
>
> Moreover, most client code should not be dependent on column order. Then a
> TETRIS option
> in VACUUM FULL would be usefull for many users.
>

lot of applications depends on column order - so this option is pretty
dangerous.

Regards

Pavel

>
> ```
> VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [TETRIS] [ table ]
> ```
>
> Does that makes sens ?
>
> Thanks,
>
> [1] https://developing.enectiva.cz/2016/05/15/postgres-column-tetris/
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message postgres user 2017-01-15 11:35:28 Re: Building PL/Perl procedural language without --with-perl configure flag
Previous Message Nicolas Paris 2017-01-15 09:58:10 Column Tetris Automatisation