Re: [PERFORM] limit clause breaks query planner?

"Tom Lane" <[EMAIL PROTECTED]> writes: > "Matt Smiley" <[EMAIL PROTECTED]> writes: > > So an Index Scan is always going to have a higher cost estimate than > > an equivalent Seq Scan returning the same result rows (unless > > random_page_cost is < 1). That's why I think the planner is alway

Re: [PERFORM] Partitions number limitation ?

On Wed, Sep 3, 2008 at 4:00 AM, <[EMAIL PROTECTED]> wrote: > Hi ! > > To improve our software insert datas performance, we have decided to use > partition architecture in our database. It works well for the following > volume : > 45 main tables and 288 inherited daughter tables for each, that is

[PERFORM] SAN and full_page_writes

I have the honor to be configuring Postgres to back into a NetApp FAS3020 via fiber. Does anyone know if the SAN protects me from breakage due to partial page writes? If anyone has an SAN specific postgres knowledge, I'd love to hear your words of wisdom. For reference: [EMAIL PROTECTED] bonnie]

[PERFORM] Partitions number limitation ?

Hi ! To improve our software insert datas performance, we have decided to use partition architecture in our database. It works well for the following volume : 45 main tables and 288 inherited daughter tables for each, that is a total of 12960 partitions. I have some trouble now with another custo

[PERFORM] dblink /synonyms?

Hello, we had problems with queries via dblink needing more than three times as long as without dblink on the same server. This has been tested with v8.3.3 as well. Is this still an issue?: http://cunha17.cristianoduarte.pro.br/postgresql/snapshots.en_us.php "But the two suffer from a severe p