Re: Cloning schemas
От | Adrian Klaver |
---|---|
Тема | Re: Cloning schemas |
Дата | |
Msg-id | e0269452-dde8-23e9-09c7-21bc95fc022e@aklaver.com обсуждение исходный текст |
Ответ на | Re: Cloning schemas (Melvin Davidson <melvin6925@gmail.com>) |
Ответы |
Re: Cloning schemas
|
Список | pgsql-general |
On 07/04/2018 03:53 PM, Melvin Davidson wrote: > > > > > The problem is, AFAICS, none of the changes induced were really > necessary or increased performance. The folks that wanted transactional ALTER SEQUENCE might disagree:): https://www.postgresql.org/docs/10/static/release-10.html "Move sequences' metadata fields into a new pg_sequence system catalog (Peter Eisentraut) A sequence relation now stores only the fields that can be modified by nextval(), that is last_value, log_cnt, and is_called. Other sequence properties, such as the starting value and increment, are kept in a corresponding row of the pg_sequence catalog. ALTER SEQUENCE updates are now fully transactional, implying that the sequence is locked until commit. The nextval() and setval() functions remain nontransactional. ... " > > > *Melvin Davidson** > Maj. Database & Exploration Specialist** > Universe Exploration Command – UXC*** > Employment by invitation only! -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: