Hi, thanks for your follow-up questions.
- postgres version is 9.1.13
- the number of rows (in this latest instance) is 28,474,842
- I've clustered and vacuum-full-ed and analyzed this table frequently,
attempting to troubleshoot this. (Running vacuum full on the whole catalog
seems a little
Hi,
On 5.3.2015 16:01, Gunnlaugur Thor Briem wrote:
Hi, thanks for your follow-up questions.
- postgres version is 9.1.13
- the number of rows (in this latest instance) is 28,474,842
- I've clustered and vacuum-full-ed and analyzed this table frequently,
attempting to troubleshoot this.
On 2/20/15 12:09 PM, Nicolas Paris wrote:
Well it seems that max query size for CREATE INDEX is 8160 character in
my 9.3 postgresql version.
Then the only solution see is to add a new boolean field : huge_table.view1
and change predicat to WHERE view1=1
But I may have 800 views.. adding 800
Tomas Vondra tomas.von...@2ndquadrant.com writes:
On 5.3.2015 16:01, Gunnlaugur Thor Briem wrote:
- postgres version is 9.1.13
The only thing I can think of is some sort of memory exhaustion,
resulting in swapping out large amounts of memory.
I'm wondering about the issue addressed by commit
On 3/4/15 1:31 PM, Soni M wrote:
Hello All,
Master db size 1.5 TB
All postgres 9.1.13 installed from RHEL package.
It has streaming replica and slony replica to another servers.
Server performance is slower than usual, before that, there's a big
query got cancelled and then performance get
What could cause this? Note that there is no ANALYZE.
Can you capture pstack and/or perf report while explain hangs?
I think it should shed light on the activity of PostgreSQL.
Vladimir
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your
On 26.02.2015 13:37, Heikki Linnakangas wrote:
On 02/26/2015 12:31 AM, Josh Berkus wrote:
On 02/14/2015 10:35 AM, Sven R. Kunze wrote:
Thanks for the immediate reply.
I understand the use case is quite limited.
On the other hand, I see potential when it comes to applications which
use
Hi, thanks for your follow-up questions.
- postgres version is 9.1.13
- the number of rows (in this latest instance) is 28,474,842
- I've clustered and vacuum-full-ed and analyzed this table frequently,
attempting to troubleshoot this. (Running vacuum full on the whole catalog
seems a little
