Finally we solved our problem by using a kind of trick
We have 2 kind of table : online table for read and temp table to mass
insert our data
We work on the temp tables (5 different tables) to insert every data
without any index that goes really fast compared to the previous method
then we
Hi,
I have a table partitioned with about 60 children tables. Now I found
the planning time of simple query with partition key are very slow.
# explain analyze select count(*) as cnt from article where pid=88 and
hash_code='2ca3ff8b17b163f0212c2ba01b80a064';
QUERY PLAN
On Wed, Jul 23, 2014 at 6:21 AM, Rural Hunter ruralhun...@gmail.com wrote:
What's wrong and how can I improve the planning performance?
What is constraint exclusion set to?
--
Douglas J Hunley (doug.hun...@gmail.com)
Von: pgsql-performance-ow...@postgresql.org
[pgsql-performance-ow...@postgresql.org]quot; im Auftrag von quot;Claudio
Freire [klaussfre...@gmail.com]
Gesendet: Freitag, 18. Juli 2014 01:21
An: Chris Ruprecht
Cc: pgsql-performance@postgresql.org
Betreff: Re: [PERFORM] Building multiple indexes on
On Wed, Jul 23, 2014 at 4:40 PM, Marc Mamin m.ma...@intershop.de wrote:
On Thu, Jul 17, 2014 at 7:47 PM, Chris Ruprecht ch...@cdrbill.com wrote:
Is there any way that I can build multiple indexes on one table without
having to scan the table multiple times? For small tables, that's probably
Hello PGSQL performance community,
[By way of introduction, we are a TPC subcommittee that is developing a
benchmark with cloud-like characteristics for virtualized databases. The
end-to-end benchmarking kit will be publicly available, and will run on PGSQL]
I am running into very high failure
It's the default value(partition):
# grep exclusion postgresql.conf
#constraint_exclusion = partition?0?2?0?2?0?2 # on, off, or partition
btw, I'm on postgresql 9.2.4
?? 2014/7/24 1:35, Douglas J Hunley :
On
On 07/24/2014 09:18 AM, Reza Taheri wrote:
What is unusual is that the majority of the failures occur in a
statement that should not have any isolation conflicts. About 17K of
failures are from the statement below:
It's not just that statement that is relevant.
At SERIALIZABLE isolation the
On 07/24/2014 09:18 AM, Reza Taheri wrote:
Does PGSQL raise locks to page level when we run with
SQL_TXN_SERIALIZABLE? Are there any knobs I can play with to alleviate
this? FWIW, the same transactions on MS SQL Server see almost no conflicts.
Also, in the documentation
