From: Tom Lane <tgl@sss.pgh.pa.us>
To: Craig Ringer <craig@postnewspapers.com.au>
Cc: Erik Jones <ejones@engineyard.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Keresztury Balázs <balazs@gaslightmusic.hu>
Cc: pgsql-performance@postgresql.org
Subject: Re: forced sequential scan when condition has current_user
Date: Tue, 05 Jan 2010 00:15:55 -0500
Message-ID: <28309.1262668555@sss.pgh.pa.us> (raw)
In-Reply-To: <4B42A068.103@postnewspapers.com.au>
References: <000f01ca8d87$88e71f30$9ab55d90$@hu>
<603c8f071001041359u58159c49k10587c7c46424672@mail.gmail.com>
<E56D1346-6E42-40D5-9CF1-239F5104F3A5@engineyard.com>
<4B42A068.103@postnewspapers.com.au>
Craig Ringer <craig@postnewspapers.com.au> writes:
> Erik Jones wrote:
>> current_user() is a stable function and the manual is explicit that the result of stable function can be used in an index scan:
> Yes ... but the planner doesn't know the value current_user will return,
I think it's got nothing to do with that and everything to do with the
fact that he's comparing to a varchar rather than text column ...
regards, tom lane
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: tgl@sss.pgh.pa.us, craig@postnewspapers.com.au, ejones@engineyard.com, robertmhaas@gmail.com, balazs@gaslightmusic.hu
Subject: Re: forced sequential scan when condition has current_user
In-Reply-To: <28309.1262668555@sss.pgh.pa.us>
* 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