| From: | Yeb Havinga <yebhavinga(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Global Sequences |
| Date: | 2012-10-16 07:33:39 |
| Message-ID: | 507D0DD3.1070100@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2012-10-15 23:33, Simon Riggs wrote:
> So, proposal is to allow nextval() allocation to access a plugin,
> rather than simply write a WAL record and increment. If the plugin is
> loaded all sequences call it (not OIDs).
+1. It is currently impossible to alter nextvals behaviour, without
making changes in core. It is possible to define an alternative
implementation and try to force to use it by using the search_path, but
serial datatypes are always bound to pg_catalog.nextval(). This would
enable every distributed PostgreSQL system to make a cleaner
implementation for global sequences than they currently have, and would
also encourage reuse of distributed nextval implementations.
regards,
Yeb
--
Yeb Havinga
http://www.mgrid.net/
Mastering Medical Data
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shigeru HANADA | 2012-10-16 08:14:36 | Re: proposal - assign result of query to psql variable |
| Previous Message | Simon Riggs | 2012-10-16 06:44:54 | Re: Global Sequences |