[GENERAL] Composite Foreign Key performance

2014-01-22 Thread Leonard Boyce
Apologies for the previous partial post earlier, fat-fingered today. If this is a repost I apologize in advance as I could not see my reply in the archive after a couple of hours. I currently have; - lookup table (lookup_id BYTEA PK, status TEXT, last_update TSTAMPTZ, ...) (PK index is > 20GB) -

Re: [GENERAL] composite foreign key performance

2014-01-22 Thread Leonard Boyce
Apologies for the previous partial post, fat-fingered today. I currently have; - lookup table (lookup_id BYTEA PK, status TEXT, last_update TSTAMPTZ, ...) (PK index is > 20GB) - data table (data_id BIGINT PK, customer_id BIGINT, lookup_id BYTEA, ...) which is partitioned by customer_id (there is

Re: [GENERAL] composite foreign key performance

2014-01-22 Thread Thomas Kellerer
Leonard Boyce, 22.01.2014 16:49: > We have an existing schema as follows; > lookup (id bytea PK, status text, .) > data A bytea as the PK? That sounds horrible. > Hoping I can get some advice here. What exactly is your question? -- Sent via pgsql-general mailing list (pgsql-general@p

[GENERAL] composite foreign key performance

2014-01-22 Thread Leonard Boyce
Hoping I can get some advice here. We have an existing schema as follows; lookup (id bytea PK, status text, .) data -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general