DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:date:message-id:subject:from:to:content-type;
	b=qBFTCVH4TSZyrLQY5SJo1L8bvXEQDB3lxKNsxjt/kcJsDew4a0OEsk8KkNafnrRlGN
	ajSF6zcdEm8MHFuvgSDCWvSUq0HnVoxsl0Swjl+wJ+fD2lorZsp5M5GXqndn7mTjn2cI
	Gy3/eM0Snl1ezrsAC5nbUo6cXbbthI2wYTq/A=
MIME-Version: 1.0
Date: Mon, 21 Dec 2009 17:15:58 -0500
Message-ID: <302670f20912211415n4fc73b04x19eebfb9ff0acd60@mail.gmail.com>
Subject: 8.4.1 distinct query WITHOUT order by
From: Gary Chambers <gwchamb@gmail.com>
To: pgsql-sql@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1

All...

One of the groups where I work uses a homegrown C/C++ application that
was written back in 7.3 days which is now running on an 8.4.1 server
(which, until very recently, was running on an 8.1 server).
Unfortunately, they did not use an order by in the query and are now
dealing with a return dataset that is unsorted and difficult to use.
The current maintainer is unsure about being able to do the right
thing and recompile the code after fixing the query.

Aside from disabling enable_hashagg (which, according to the
documentation, is performance-expensive), what other options do I
have?

What are the ramifications of renaming the table (containing 8000
rows) and creating a view of the same name?

Assuming it's possible, would the efficiency of a rule to rewrite the
query be an acceptable alternative?

Thanks in advance for any insight and suggestions!

-- Gary Chambers

/* Nothing fancy and nothing Microsoft! */