pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Andy Colson <andy@squeakycode.net>
To: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Running PostgreSQL as fast as possible no matter the consequences
Date: Mon, 15 Nov 2010 13:27:43 -0600
Message-ID: <4CE189AF.6020308@squeakycode.net> (raw )
In-Reply-To: <AANLkTi=4YuXEphsR3XW3Ua=eQGnvbpPsx7hf0T9sVi3C@mail.gmail.com >
References: <AANLkTimcUYuutQeThCaP-077reGYWwdq-ssKwbPne8TO@mail.gmail.com >
<AANLkTikVBTRkZCTiqzwRYemJhHLvwwrnA1WHguBpc5Qp@mail.gmail.com >
<AANLkTin+ZRe5mEOj72ga8xOfbULpYn6kwH4hy_JCBYm2@mail.gmail.com >
<AANLkTi=9CL-O=D_eiCxx7R=1zkGhimAotnGgB_WsvC2-@mail.gmail.com >
<87hbfwvupx.fsf@meuh.mnc.lan >
<AANLkTim5RaimYK15UdGvkgG_8KhCJdt_QguNLgxKh63Q@mail.gmail.com >
<AANLkTi=4YuXEphsR3XW3Ua=eQGnvbpPsx7hf0T9sVi3C@mail.gmail.com >
On 11/15/2010 9:06 AM, Robert Haas wrote:
> In 9.1, I'm hopeful that we'll have unlogged tables, which will even
> better than turning these parameters off, and for which I just posted
> a patch to -hackers. Instead of generating WAL and writing WAL to the
> OS and then NOT trying to make sure it hits the disk, we just won't
> generate it in the first place. But if PostgreSQL or the machine it's
> running on crashes, you won't need to completely blow away the cluster
> and start over; instead, the particular tables that you chose to
> create as unlogged will be truncated, and the rest of your data,
> including the system catalogs, will still be intact.
>
if I am reading this right means: we can run our db safely (with fsync
and full_page_writes enabled) except for tables of our choosing?
If so, I am very +1 for this!
-Andy
view thread (31+ messages) latest in thread
Message-ID: <4CE189AF.6020308@squeakycode.net>
Permalink: ../4CE189AF.6020308@squeakycode.net/
Also on: postgresql.org/message-id/4CE189AF.6020308@squeakycode.net
copy link · copy postgr.es
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: andy@squeakycode.net, robertmhaas@gmail.com
Subject: Re: Running PostgreSQL as fast as possible no matter the consequences
In-Reply-To: <4CE189AF.6020308@squeakycode.net>
* 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