| From: | Curt Sampson <cjs(at)cynic(dot)net> |
|---|---|
| To: | "J(dot) R(dot) Nield" <jrnield(at)usol(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Index Scans become Seq Scans after VACUUM ANALYSE |
| Date: | 2002-06-25 03:32:05 |
| Message-ID: | Pine.NEB.4.43.0206251229010.17448-100000@angelic.cynic.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 24 Jun 2002, J. R. Nield wrote:
> All I'm saying is that the entire postgresql block write must be
> converted into exactly one SCSI write command in all cases, and I don't
> know a portable way to ensure this.
No, there's no portable way. All you can do is give the admin who
is able to set things up safely the ability to turn of the now-unneeded
(and expensive) safety-related stuff that postgres does.
> I agree with this. My point was only that you need to know what
> guarantees your operating system/hardware combination provides on a
> case-by-case basis, and there is no standard way for a program to
> discover this. Most system administrators are not going to know this
> either, unless databases are their main responsibility.
Certainly this is true of pretty much every database system out there.
cjs
--
Curt Sampson <cjs(at)cynic(dot)net> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2002-06-25 03:32:44 | Re: Request for builtin function: Double_quote |
| Previous Message | Thomas Lockhart | 2002-06-25 02:19:06 | Re: Nonrecursive ALTER TABLE ADD/RENAME COLUMN is wrong |