Re: [PERFORM] printing results of query to file in different times

Hi Mariel, On 9/6/2017 4:38 AM, Mariel Cherkassky wrote: I'm sure that those tables arent involved in any other transaction when the loop is running. Anything else that I can check ? I think that mybe its connected to some fetching properties but Im not familiar with what settings.. That's

Re: [SPAM] [PERFORM] OS cache management

Il 06/09/2017 10:12, Soni M ha scritto: Let's say I have 10 year data, and commonly used data only the last 1 year. This data is quite big, so each table and index file is divided into several file in PGDATA/base May not be relevant to what you asked, but if you want to keep last yeat

Re: [PERFORM] OS cache management

- Mensaje original - > De: "Soni M" > Para: pgsql-performance@postgresql.org > Enviados: Miércoles, 6 de Septiembre 2017 5:12:26 > Asunto: [PERFORM] OS cache management > > Hello All, I would like to know about how OS cache works for postgres table > and index

[PERFORM] Slow vacuum of GIST indexes, because of random reads on PostgreSQL 9.6

I am using a GIST index on timestamp range, because it supports 'contains' operator ('@>'). Unfortunately, in large scale (billions of rows, index size: almost 800 GB) vacuuming the index takes an order of magnitude longer than btrees (days/weeks instead of hours). According to the code, during

[PERFORM] OS cache management

Hello All, I would like to know about how OS cache works for postgres table and index file. Let's say I have 10 year data, and commonly used data only the last 1 year. This data is quite big, so each table and index file is divided into several file in PGDATA/base Let's say 1 index named