Re: Collect frequency statistics for arrays - Mailing list pgsql-hackers

From Nathan Boley
Subject Re: Collect frequency statistics for arrays
Date
Msg-id CAHetpQQDNgPaf2WvwC5zL0erSFmueDS3UdcYkD5ZmnPOGT-uMQ@mail.gmail.com
Whole thread Raw
In response to Re: Collect frequency statistics for arrays  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Collect frequency statistics for arrays  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>> What about MCV's? Will those be removed as well?
>
> Sure.  Those seem even less useful.

Ya, this will destroy the performance of several queries without some
heavy tweaking.

Maybe this is bad design, but I've gotten in the habit of storing
sequences as arrays and I commonly join on them. I looked through my
code this morning, and I only have one 'range' query ( of the form
described up-thread ), but there are tons of the form

SELECT att1, attb2 FROM rela, relb where rela.seq_array_1 = relb.seq_array;

I can provide some examples if that would make my argument more compelling.

Sorry to be difficult,
Nathan


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Allowing multi "-t" and adding "-n" to vacuumdb ?
Next
From: Tom Lane
Date:
Subject: Re: Collect frequency statistics for arrays