pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Rob Nagler <nagler@bivio.biz>
To: pgsql-performance@postgresql.org
Subject: Re: vacuum locking
Date: Wed, 29 Oct 2003 16:55:07 -0800
Message-ID: <200310291655.07363.josh@agliodbs.com> (raw)
In-Reply-To: <16288.19970.172547.319577@jump.bivio.com>
References: <16272.318.870000.93584@gargle.gargle.HOWL>
	<87d6ciy3bf.fsf@stark.dyndns.tv>
	<16288.19970.172547.319577@jump.bivio.com>

Rob,

> q5 and q6 are too complex to discuss here, but the fundamental issue
> is the order in which postgres decides to do things.  The choice for
> me is clear: the developer time trying to figure out how to make the
> planner do the "obviously right thing" has been too high with
> postgres.  These tests demonstate to me that for even complex queries,
> oracle wins for our problem.
> 
> It looks like we'll be migrating to oracle for this project from these
> preliminary results.  It's not just the planner problems.  The
> customer is more familiar with oracle, and the vacuum performance is
> another problem.

Hey, we can't win 'em all.   If we could, Larry would be circulating his 
resume'.

I hope that you'll stay current with PostgreSQL developments so that you can 
do a similarly thourough evaluation for your next project.

-- 
-Josh Berkus
 Aglio Database Solutions
 San Francisco




view thread (45+ messages)  latest in thread

Message-ID: <200310291655.07363.josh@agliodbs.com>
Permalink:  ../200310291655.07363.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200310291655.07363.josh@agliodbs.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: josh@agliodbs.com, nagler@bivio.biz
  Subject: Re: vacuum locking
  In-Reply-To: <200310291655.07363.josh@agliodbs.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