On 28/07/16 17:52, Jason Dusek wrote:
With regards to write amplification, it makes me think about about
OIDs. Used to be, every row had an OID and that OID persisted across
row versions.
https://www.postgresql.org/docs/9.5/static/runtime-config-compatible.html#GUC-DEFAULT-WITH-OIDS
Would reintroducing such a feature address some of Uber's concerns
about multiple indexes? It could, and would do so without the implicit
requirement of a foreign key; but it would also require a fast OID to
CTID mapping.
On Tue, 26 Jul 2016 at 10:40 Guyren Howe <guy...@gmail.com
<mailto:guy...@gmail.com>> wrote:
Honestly, I've never heard of anyone doing that. But it sounds
like they had good reasons.
https://eng.uber.com/mysql-migration/
Thoughts?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org
<mailto:pgsql-general@postgresql.org>)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Would it be best to increase OIDs to 64 bits?
Possibly a choice of 32/64 to be decided when the DB is created???
Cheers,
Gavin
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
