Scott Cain [EMAIL PROTECTED] writes:
I see, encoding is a per database option. Since I've never set it, all
my databases use sql_ascii.
Okay, then you've dodged the obvious bullet; time to try profiling I
guess. The way I usually do it is (given a clean, configured source
tree):
cd
On Thu, Jul 31, 2003 at 02:51:45PM -0500, Jim C. Nasby wrote:
Why is pgsql estimating a cost of 1 for retire_today in this
query? I analyzed it, and there's nothing very odd about it, other than
it's a temp table.
BTW, I had to set enable_seqscan=false to get this, otherwise it wants
Orignally there were but in the process of trying to figure
out what is going on I stripped everything out of the database
except the table being queried.
Medora Schauer [EMAIL PROTECTED] writes:
I have a table with a 3 column key. I noticed that when I
update a non-key field
in a
This is stepping back quite a while; let me point people to the thread
of 2003-02 where Mariusz Czu\x{0142}ada [EMAIL PROTECTED] was
looking for a way of optimizing a VIEW that was a UNION.
http://archives.postgresql.org/pgsql-performance/2003-02/msg00095.php
The subject has come up a few times
On Thu, Jul 31, 2003 at 04:59:21PM -0400, Andrew Sullivan wrote:
On Thu, Jul 31, 2003 at 02:51:45PM -0500, Jim C. Nasby wrote:
If you really needed to set enable_seqscan=false (did you really?
Are you sure that's not the cheapest way?), you might want to
investigate expainding the statistics
Stephan Szabo wrote:
On Thu, 31 Jul 2003, Christopher Browne wrote:
select * from log_table where request_time between 'june 11 2003' and
'june 12 2003';
returns a plan:
Subquery Scan log_table (cost=0.00..10950.26 rows=177126 width=314)
-
