Re: [GENERAL] My index doesn't write anymore but read

2015-05-17 Thread Andreas Kretschmer
ben.play wrote: > Hi all, > > We have a large database with postgre 9.3 (>300 Gb) and our queries are > (really) long for 6 days without changing anything. > > After seeing our log, I saw that the same query on an old data was quick but > the same query with new data are really slow. please

[GENERAL] My index doesn't write anymore but read

2015-05-17 Thread ben.play
Hi all, We have a large database with postgre 9.3 (>300 Gb) and our queries are (really) long for 6 days without changing anything. After seeing our log, I saw that the same query on an old data was quick but the same query with new data are really slow. Let me show you a sample of my query on

Re: [GENERAL]

2015-05-17 Thread William Dunn
Hello Sachin, I hate to respond by suggesting an alternative but it may be good to try using pg_basebackup (Doc: http://www.postgresql.org/docs/9.1/static/app-pgbasebackup.html) to back-up your database. It takes a copy of the file system files rather than querying the data as an ordinary connecti

Re: [GENERAL] SELECT .. WHERE id IN(..)

2015-05-17 Thread William Dunn
Hello Maks, As I think Sam suspects the issue might be that you may not have enough RAM, or not enough RAM is allocated to shared_buffers, or you may have this table's data being evicted from shared_buffers because of some other queries, so while you are identifying all the rows in your fast index