[HACKERS] SET NOT NULL [NOT VALID / CONCURRENTLY]?
От
Joel Jacobson
Тема
[HACKERS] SET NOT NULL [NOT VALID / CONCURRENTLY]?
Дата
Msg-id
CAASwCXcOokBqHf8BXECbDgOLkXxJyL_Q_twhg2dGWSvgMzz=xA@mail.gmail.com
Список
Дерево обсуждения
[HACKERS] SET NOT NULL [NOT VALID / CONCURRENTLY]? Joel Jacobson <joel@trustly.com>
Re: [HACKERS] SET NOT NULL [NOT VALID / CONCURRENTLY]? Craig Ringer <craig@2ndquadrant.com>
Re: [HACKERS] SET NOT NULL [NOT VALID / CONCURRENTLY]? Joel Jacobson <joel@trustly.com>
Re: [HACKERS] SET NOT NULL [NOT VALID / CONCURRENTLY]? Craig Ringer <craig@2ndquadrant.com>
Re: [HACKERS] SET NOT NULL [NOT VALID / CONCURRENTLY]? Joel Jacobson <joel@trustly.com>
Re: [HACKERS] SET NOT NULL [NOT VALID / CONCURRENTLY]? Joel Jacobson <joel@trustly.com>
Re: [HACKERS] SET NOT NULL [NOT VALID / CONCURRENTLY]? Robert Haas <robertmhaas@gmail.com>
Hi hackers, I would be good if it would be possible to quickly set NOT NULL for an existing column in a table that have no rows where the column IS NULL and where there is a full index on the column allowing the logics to quickly understand there are no NULL values, and just have to take a quick lock on the table to prevent any modifications during the short time when the NOT NULL is set for the column. Currently if you want to set NOT NULL for a column in a huge table that's not doable without blocking all writes to the table for quite some time. Setting NOT NULL for a 100 million row table took 28 seconds locally on my machine. Is anyone working on fixing this for PostgreSQL 10? Joel Jacobson Trustly
В списке pgsql-hackers по дате отправления
От: Kyotaro HORIGUCHI
Дата: