| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
| Cc: | DiasCosta <diascosta(at)diascosta(dot)org>, Łukasz Jarych <jaryszek(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Cloning schemas |
| Date: | 2018-07-04 23:00:42 |
| Message-ID: | e0269452-dde8-23e9-09c7-21bc95fc022e@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melvin Davidson | 2018-07-04 23:08:46 | Re: Cloning schemas |
| Previous Message | Melvin Davidson | 2018-07-04 22:53:17 | Re: Cloning schemas |