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

Re: PostgreSQL does CAST implicitely between int and a domain derived from int

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <pgsql-performance(at)postgresql(dot)org>,<jm(at)poure(dot)com>, "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Subject: Re: PostgreSQL does CAST implicitely between int and a domain derived from int
Date: 2009-08-26 23:27:29
Message-ID: 4A957E91020000250002A372@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-performance
I wrote:
 
> I will take another look at it now that you have the results of
> EXPLAIN ANALYZE posted
 
Could you run this?:
 
set work_mem = '50MB';
set effective_cache_size = '3GB';
EXPLAIN ANALYZE <your query>
begin transaction;
drop index node_comment_statistics_node_comment_timestamp_idx;
EXPLAIN ANALYZE <your query>
rollback transaction;
 
The BEGIN TRANSACTION and ROLLBACK TRANSACTION will prevent the index
from actually being dropped; it just won't be visible to your query
during that second run.  I'm kinda curious what plan it chooses
without it.
 
Some configuration options can be dynamically overridden for a
particular connection.  This is not a complete list of what you might
want to use in your postgresql.conf file, but it might turn up an
interesting plan for diagnostic purposes.
 
-Kevin


In response to

Responses

pgsql-performance by date

Next:From: Jean-Michel PouréDate: 2009-08-27 13:36:10
Subject: Re: PostgreSQL does CAST implicitely between int and a domain derived from int
Previous:From: Kevin GrittnerDate: 2009-08-26 23:03:07
Subject: Re: PostgreSQL does CAST implicitely between int and a domain derived from int

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