| From: | Thomas Poty <thomas(dot)poty(at)gmail(dot)com> |
|---|---|
| To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: dealing with lock |
| Date: | 2018-04-07 07:57:49 |
| Message-ID: | CAN_ctngdfzdTb-P9rtuu_-KJOkXnP=e-vjzKsB_FBDk-z5Uymg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thank you Thomas
Regards
Thomas
Le sam. 7 avr. 2018 à 08:01, Thomas Kellerer <spam_eater(at)gmx(dot)net> a écrit :
> Adrian Klaver schrieb am 07.04.2018 um 00:02:
> >> Is there a way to identify the list of statements that have to rewrite
> the table.
> >
> > https://www.postgresql.org/docs/10/static/sql-altertable.html
> >
> > Notes
> >
> > "Adding a column with a DEFAULT clause or changing the type of an
> existing column will require the entire table and its indexes to be
> rewritten.
> Note that this will change with Postgres 11
>
>
> https://www.depesz.com/2018/04/04/waiting-for-postgresql-11-fast-alter-table-add-column-with-a-non-null-default/
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Đỗ Ngọc Trí Cường | 2018-04-07 10:44:13 | Conflict between JSON_AGG and COPY |
| Previous Message | Thomas Poty | 2018-04-07 07:56:45 | Re: dealing with lock |