Skip site navigation (1) Skip section navigation (2)

Re: Collect frequency statistics for arrays

From: Nathan Boley <npboley(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Collect frequency statistics for arrays
Date: 2012-03-01 22:16:53
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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,

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2012-03-01 22:19:22
Subject: Re: Collect frequency statistics for arrays
Previous:From: Tom LaneDate: 2012-03-01 22:13:35
Subject: Re: Allowing multi "-t" and adding "-n" to vacuumdb ?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group