Hi,
depending on the OFFSET parameter I have seen at least 3 different query
plans.
SELECT * FROM
(
SELECT * FROM transaction tt
WHERE
tt.account_id = '1376641'
AND tt.transaction_time >= '2013-02-03 05:37:24'
AND tt.transaction_time < '2013-08-23 05:37:24
On 09/02/2013 05:53 AM, Łukasz Walkowski wrote:
On 1 wrz 2013, at 05:10, Vitalii Tymchyshyn wrote:
Well, there are some more options:
a) Store int keys and do mapping in the application (e.g. with java enums).
This can save you a join, that is especially useful if you are going to do
paged
On 1 wrz 2013, at 05:10, Vitalii Tymchyshyn wrote:
>
>
> Well, there are some more options:
> a) Store int keys and do mapping in the application (e.g. with java enums).
> This can save you a join, that is especially useful if you are going to do
> paged output with limit/offset scenario. Opt
On 1 wrz 2013, at 03:31, Craig James wrote:
> If your applications are read-heavy and only have a small-ish amount of code
> that inserts/updates the table, it may not be that much of a rewrite. You can
> create a integer/varchar table of key/values, use its key to replace the
> current varch
bsreejithin wrote:
>
> I am *expecting 1000+ hits to my PostgreSQL DB* and I doubt my standalone DB
> will be able to handle it.
>
> So I want to *scale out by adding more servers to share the load*. For this,
> I want to do clustering.
>
> DB server was 4 Core 12GB RAM.
You're jumping way ahea
On 08/30/2013 01:48 AM, bsreejithin wrote:
> Ya..sure...Migration to 9.2 is one of the activities planned and in fact
> it's already on track.Thanks Thomas
You'll want to re-do your performance testing; a huge amount has changed
since 8.2.
--
Craig Ringer http://www.2ndQuadra
