On Thu, 4 Jul 2002, Tom Lane wrote:
> I can think of very very few applications where CHAR(n) is really a
> sensible choice over VARCHAR(n).
text hashes such as MD5 and crypt, stock or serial numbers, automotive
VIN codes, invoice sequences, emulated bitmasks, etc. Lots of
industry-specific
On Mon, 3 Dec 2001, Manuel Trujillo wrote:
> SELECT d.gallery_id, e.subevent_id, d.result_type_id,
> d.result_type_name, e.language_id FROM ((SELECT b.gallery_id,
> b.element_id AS result_type_id, c.name AS result_type_name FROM
> gallery_element b, result_type c WHERE ((c.id = b.element_id) AND
On 31 Aug 2001, Raquel Vieira wrote:
> Does anyone know how can I start postmaster (at the startup of the
> computer) with the option -i?
The file that is starting postgres is one of these:
/etc/rc.d/init.d/postgresql
/etc/rc.d/init.d/postgres
/etc/rc.d/init.d/postgresd
The last one is the mos
Hello, again.
Is there some way to turn off notices in postgres's logging? We have a
sloppy programmer who wrote queries that cause postgres to print
messages like:
Adding missing FROM-clause entry for table "table_name"
This application is used by hundreds of our customers, and hence gets lot
On Fri, 18 May 2001, Tom Lane wrote:
> Given the inherent inaccuracy of the cost estimates, I'd be real
> hesitant to rely on them to suppress overly-expensive queries.
That's just it. You don't have to be that accurate. If an estimate
goes into the millions or billions, something is obviously
Hey all,
I can't seem to find it in the docs, so I'll ask here. Is there a
way in postgres to impose a limit on query costs? I'd noticed some
horribly disfigured queries hitting my poor database from one of our
developers, and corrected him. But many of our users are not so
easily contacted.
