From: | Tom DalPozzo <t(dot)dalpozzo(at)gmail(dot)com> |
---|---|
To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: WAL being written during SELECT * query |
Date: | 2017-04-10 16:31:55 |
Message-ID: | CAK77FCT1SmJ3yJb-eiX=gxDXDh2aq+vtRRMaOOHtaBUXMwi9iA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2017-04-10 16:49 GMT+02:00 Bill Moran <wmoran(at)potentialtech(dot)com>:
>
> > >> On Tue, Apr 4, 2017 at 9:46 AM, Tom DalPozzo <t(dot)dalpozzo(at)gmail(dot)com>
> > >> wrote:
> > >> > Hi,
> > >> > I have a very big table (10GB).
> > >> > I noticed that many WAL segments are being written when elaborating
> read
> > >> > only transactions like this:
> > >> > select * from dati25600000000 where id >43000000 limit 1000000;
> > >> > I don't understand why are there WAL writings during read only
> > >> transactions.
>
> These are hint bits. The mechanism and behavior are known and documented:
> https://wiki.postgresql.org/wiki/Hint_Bits
>
> --
> Bill Moran <wmoran(at)potentialtech(dot)com>
>
Hi, OK! Thank you very much
Pupillo
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2017-04-10 16:33:28 | Re: Are multiple array_aggs going to be in the same order? |
Previous Message | Moreno Andreo | 2017-04-10 15:59:46 | Re: PostgreSQL and Kubernetes |