| From: | Anton Melser <melser(dot)anton(at)gmail(dot)com> |
|---|---|
| To: | Adam Pearson <Adam(dot)Pearson(at)4finance(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Plan differences |
| Date: | 2016-01-04 13:30:30 |
| Message-ID: | CAKywjPruzKfsMmZ5vgfOp5VG-OAaJow7MQBho2m3NbhETrvNKw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Hi,
> Changing the locale to anything other than C or POSIX will
> have a performance overhead. I’m pretty sure that just declaring the
> locale on the indexes is just like plastering over the cracks.
>
>
>
> Is it possible to reload the database with the same locale as the original
> database server?
>
Sorry, I wasn't clear - I did end up recreating the DB with lc_collate =
"C" and lc_ctype = "C" and loading all data and the plans are for this
situation (i.e., both are now the same, "C" everywhere) Maybe it is just a
case of optimisations being removed in the RC?
Cheers,
Anton
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yves Dorfsman | 2016-01-04 14:27:52 | Re: Proposal for unlogged tables |
| Previous Message | Mark Zealey | 2016-01-04 09:59:56 | Proposal for unlogged tables |