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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
