On Thu, Apr 4, 2019 at 10:48 AM Prasad wrote:
> Hi,
>
> I have installed PostgreSQL 9.4 (open source) version on my CentOS Linux
> Red Hat 7 production server and kept default parameters which are in
> postgresql.conf file.So my basic question is, once I start using postgres
> how much RAM the po
bal index support feels like it has potential to resolve many of the issues
I have with partitioning (beyond the optimizer concern above). I assume this
has been discussed and rejected though by the community?
I've attached as a file the original test script.
Keith
On Friday, 8 February 2
e partition statistics for the partition level access strategy, but
the global statistics when estimating the actual rows returned by all the
individual partition queries. Is there a reason not to do this? Or do others
believe the optimizer is doing the right thing here?
And then some general questions:
- How do other people use partitioning but without a significant performance
disadvantage on reading the data? Is there something else I should be doing
here to achieve the same thing without the overhead? At present my reads have
increased optimization cost (as it needs to optimize access to each partition)
and also execution cost (access the index on every partition). Even without the
optimizer issues described above, the cost of reading simple data is extremely
high relative to non-partitioned data (unless you use the partition key as a
filter for each table to eliminate those partitions).- Is there any chance/plan
to add global indexes to postgres? If so would that impact significantly the
cost of the partition drop e.g. to clean up the index.
Thanks in advance for any feedback/support,
Keith
