On Tue, Feb 22, 2011 at 10:18:36PM -0500, Robert Haas wrote:
> On Wed, Feb 2, 2011 at 12:20 AM, Noah Misch wrote:
> >> CREATE TABLE account (account_id SERIAL PRIMARY KEY, name CHARACTER VARYING
> >> NOT NULL);
> >> CREATE TABLE foo (account_id INTEGER NOT NULL REFERENCES account
> >> (account_id)
Robert Haas writes:
> The problem is that constraints can affect the query plan. If a
> transaction sees the constraint in the system catalogs (under
> SnapshotNow) but the table data doesn't conform (under some earlier
> snapshot) and if the chosen plan depends on the validity of the
> constrain
On Wed, Feb 2, 2011 at 12:20 AM, Noah Misch wrote:
>> CREATE TABLE account (account_id SERIAL PRIMARY KEY, name CHARACTER VARYING
>> NOT NULL);
>> CREATE TABLE foo (account_id INTEGER NOT NULL REFERENCES account
>> (account_id), stuff CHARACTER VARYING);
>
>> DROP TABLE foo;
>
>> That query shows
On Fri, Feb 4, 2011 at 7:08 AM, Ivan Voras wrote:
> -> BitmapAnd (cost=1282.94..1282.94
> rows=1430 width=0) (actual time=5.508..5.508 rows=0 loops=1)
> -> Bitmap Index Scan on
> news_index_layout_id_state (cost=0.00..150.14
On Wed, Feb 16, 2011 at 4:22 PM, Bruce Momjian wrote:
> I am not excited about the idea of putting these correlations in
> queries. What would be more intesting would be for analyze to build a
> correlation coeffficent matrix showing how columns are correlated:
>
> a b c
> a 1 .
