From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | fran(at)reyes(dot)somos(dot)net |
Cc: | aa2(at)bigpond(dot)net(dot)au, mykarz(at)miyabara(dot)com, pgsql-novice(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Re: [NOVICE] Re: Sizing of LARGE databases. |
Date: | 2001-02-07 01:12:58 |
Message-ID: | 20010207101258V.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-novice |
> On Wed, 31 Jan 2001, Justin Clift wrote:
> > The biggest limitation I have found with this is the
> > /opt/postgres/data/pg_log file seeming to need to log (write) bunches of
> > data, even when just doing searches (reads) on indexes on other tables.
This is not true.
1) We do not write "bunches of data" into pg_log. We write just 2 bits
per transaction.
2) Simple read-only SELECT does not write pg_log at all.
--
Tatsuo Ishii
From | Date | Subject | |
---|---|---|---|
Next Message | Brice Ruth | 2001-02-07 01:18:19 | Re: [SQL] Re: SQL Join - MySQL/PostgreSQL difference? |
Previous Message | Brice Ruth | 2001-02-07 01:06:24 | Re: [SQL] Re: SQL Join - MySQL/PostgreSQL difference? |
From | Date | Subject | |
---|---|---|---|
Next Message | Conrad Schuler | 2001-02-07 01:49:25 | When do you separate databases? |
Previous Message | info | 2001-02-07 00:19:51 | Re: General Database Design Text |