From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
Cc: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, Don Baccus <dhogaza(at)pacifier(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] The dangers of "-F" |
Date: | 1999-06-23 14:10:26 |
Message-ID: | 21070.930147026@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> Is there any chance each database could be setup differently? Some of
> my databases are updated once a month (literally), while others are
> updated daily. It would be nice to have the -F setting on the
> read-mostly DBs...
I don't think this is practical, because all the backends in a given
installation will be sharing the same buffer cache and the same pg_log
file; you can't run some with -F and some without and expect to get
the behavior you want. Problem is that any of the backends might be
the one that writes out a particular disk block from cache.
You could run the two sets of databases as different installations
(ie, two postmasters, two listen ports, two working directories)
but that'd require all your clients knowing which port to connect to
for each database; probably not worth the trouble.
In practice, if you have a reliable OS, reliable hardware, and a
reliable power supply (read UPS), I think the risks introduced by
running with -F are negligible compared to other sources of trouble
(ie backend bugs)...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Collin F. Lynch | 1999-06-23 15:33:49 | Images |
Previous Message | Philip Warner | 1999-06-23 12:04:09 | Re: [HACKERS] The dangers of "-F" |