2017-04-10 16:49 GMT+02:00 Bill Moran :
>
> > >> On Tue, Apr 4, 2017 at 9:46 AM, Tom DalPozzo
> > >> 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:
> > >> > sele
> >> On Tue, Apr 4, 2017 at 9:46 AM, Tom DalPozzo
> >> 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 dati256 where id >4300 limit 100
2017-04-06 17:51 GMT+02:00 Tom DalPozzo :
>
>
> 2017-04-04 19:18 GMT+02:00 Scott Marlowe :
>
>> On Tue, Apr 4, 2017 at 9:46 AM, Tom DalPozzo
>> wrote:
>> > Hi,
>> > I have a very big table (10GB).
>> > I noticed that many WAL segments are being written when elaborating read
>> > only transactions
On Thu, Apr 6, 2017 at 8:51 AM, Tom DalPozzo wrote:
>
> What is the meaning of FPI_FOR_HINT?
>
>
Full Page Image for Hint [Bits]
Its noted as being dependent upon checksums being enabled.
I have a feel for the interactions involved here but not enough to explain
them in detail.
David J.
2017-04-04 19:18 GMT+02:00 Scott Marlowe :
> On Tue, Apr 4, 2017 at 9:46 AM, Tom DalPozzo 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 dati256 where id >43
On Tue, Apr 4, 2017 at 9:46 AM, Tom DalPozzo 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 dati256 where id >4300 limit 100;
> I don't understand why are there
On 04/04/17 16:46, Tom DalPozzo 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 dati256 where id >4300 limit 100;
I don't understand why are there WAL writings during rea
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 dati256 where id >4300 limit 100;
I don't understand why are there WAL writings during read only transactions.
Regards
Pupillo
