| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | frank <halldu0815(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Will modifications to unlogged tables also be flused to disk? |
| Date: | 2014-12-08 17:55:39 |
| Message-ID: | CAMkU=1xc2NAJD192QfkQj3sn+gtzXtp-7UoziKimNp0tWBNKoQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Dec 8, 2014 at 4:43 AM, frank <halldu0815(at)gmail(dot)com> wrote:
> Jeff Janes wrote
> > That's not really true. There are no per-row WAL records. There is
> still
> > a per-transaction WAL record, the commit record. If you only care about
> > the
> > timing of the WAL and not the volume, changing to unlogged will not make
> a
> > difference. (These commit-only records are automatically dealt with
> > asynchronously, even if synchronous-commit is on.)
> >
> > Cheers,
> >
> > Jeff
>
> Hi,
>
> just to understand this answer:
>
> Is it *NOT* possible to create an unlogged table where inserts or updates
> will *NOT* modify the WAL files?
>
>
Correct.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Edson Richter | 2014-12-08 18:13:50 | Divergences in view source code - both servers 9.3.5 |
| Previous Message | Andy Colson | 2014-12-08 16:38:39 | Re: Removing duplicate records from a bulk upload |