pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christopher Sawtell <csawtell@xtra.co.nz>
Cc: pgsql-sql@postgreSQL.org <pgsql-sql@postgresql.org>
Subject: Re: Counting distinct names
Date: Wed, 19 Apr 2000 22:50:24 -0400
Message-ID: <303.956199024@sss.pgh.pa.us> (raw)
In-Reply-To: <00042014371500.19753@berty>
References: <38FBBD02.4424CB34@nsi.edu>
	<38FCACFC.55B12EB0@nsi.edu>
	<22328.956120719@sss.pgh.pa.us>
	<00042014371500.19753@berty>

Christopher Sawtell <csawtell@xtra.co.nz> writes:
> 1) There are files on the ftp sites which seem to be the "whole thing"
> and what I suppose is the "whole thing" cut up into smaller sections.

Yes.

>   Am I correct? Or do I need to d/l the smaller files as well?
>   A README_for_Download might be a good idea.

Yo, Marc ... where's the documentation about the new tarfile sections?

> 2) I couldn't find a --database-dir=[/var/lib/pgsql/data] option in
> the output from ./configure --help.  How can one configure pg to place
> it's database in a defined place in the file system? btw the default
> of /var/lib/pgsql/data seems pretty sensible.

The default location is PREFIX/data; I don't think there is a configure
option to change that without setting --prefix.  However, you can set it
at runtime with the -D options to initdb and postmaster, so adding yet
another configure switch might be gilding the lily.

> 3) Some of the scripts and binary files for the subsiduary tools have
> to be installed by hand. If you need to know what, I'd be happy to
> re-install pg and take notes.

News to me, other than that the perl interface module usually has to be
installed separately because of permission issues.  What did you see
missing?

> 5) Is the idea of putting the data on a raw partition on the horizon?

Not really.  There are portability issues with that; furthermore, it's
not obvious that it'd be better.  The system's been developed and tuned
to sit atop a Unix kernel's disk cache.  Writing our own disk management
code would be a large investment of work and a large loss of portability
for very questionable benefits.  It might happen someday, but I think
we have many higher-priority tasks ahead...

			regards, tom lane



view thread (12+ messages)  latest in thread

Message-ID: <303.956199024@sss.pgh.pa.us>
Permalink:  ../303.956199024@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/303.956199024@sss.pgh.pa.us

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, csawtell@xtra.co.nz
  Subject: Re: Counting distinct names
  In-Reply-To: <303.956199024@sss.pgh.pa.us>
  References: <38FBBD02.4424CB34@nsi.edu> <38FCACFC.55B12EB0@nsi.edu> <22328.956120719@sss.pgh.pa.us> <00042014371500.19753@berty> <303.956199024@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