| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Doug Fields <dfields-pg-general(at)pexicom(dot)com> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, petedaly(at)ix(dot)netcom(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Non-linear Performance |
| Date: | 2002-06-10 16:12:08 |
| Message-ID: | 200206101612.g5AGC9M15932@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Doug Fields wrote:
> At 08:11 AM 6/10/2002, Martijn van Oosterhout wrote:
> >there is no speed overhead. I'd be interested to know how MVCC would be
> >slowing anything down.
>
> I'd be interested in being able to turn it off and see if it speeds
> anything up. :)
>
> I didn't mean to imply that I _know_ that it slows things down. What I do
> know is that I a_ssume_ it does, and would like to be able to selectively
> disable it - in the hope of gaining speed at certain points. I figure the
> biggest speed gain will be because PostgreSQL can then skip writing
> anything to the transaction log. But then again, I also do not _know_ that.
MVCC is an integral part of how PostgreSQL's no-overwriting storage
manager works. It can't be turned of, and if it could, it wouldn't
provide _any_ speed increase.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vincent Stoessel | 2002-06-10 17:01:36 | Re: size of units in postgresql.conf |
| Previous Message | Stephan Szabo | 2002-06-10 16:10:42 | Re: [SQL] VIEWs and FOREIGN keys |