pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dave Dutcher <dave@tridecap.com>
To: 'Vincenzo Romano' <vincenzo.romano@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: Weird performance drop
Date: Fri, 30 Mar 2007 09:34:10 -0500
Message-ID: <01ea01c772d8$7b87aca0$2e00a8c0@tridecap.com> (raw)
In-Reply-To: <200703300836.16601.Vincenzo.Romano@gmail.com>

> From: pgsql-performance-owner@postgresql.org 
> [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of 
> Vincenzo Romano
> 
> Is there any "workaround"?
> 
> In my opinion the later the query planner decisions are taken the more
> effective they can be.
> It could be an option for the function (body) to delay any 
> query planner
> decision.

I think a possible workaround is to use a plpgsql function and the execute
statement. The docs will have more info.

Dave





view thread (5+ messages)  latest in thread

Message-ID: <01ea01c772d8$7b87aca0$2e00a8c0@tridecap.com>
Permalink:  ../01ea01c772d8$7b87aca0$2e00a8c0@tridecap.com/
Also on:    postgresql.org/message-id/01ea01c772d8$7b87aca0$2e00a8c0@tridecap.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: dave@tridecap.com, vincenzo.romano@gmail.com
  Subject: Re: Weird performance drop
  In-Reply-To: <01ea01c772d8$7b87aca0$2e00a8c0@tridecap.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox