On Wed, Mar 26, 2008 at 10:09 PM, Shane Ambler <[EMAIL PROTECTED]> wrote: > Scott Marlowe wrote: > > On Wed, Mar 26, 2008 at 1:48 PM, p prince <[EMAIL PROTECTED]> wrote: > >> is this 'normal'? (loaded question I know) > >> Should I be looking to offload expensive reporting queries to read-only > >> replicants of my database? > > > > Yes, definitely look into setting up something like a slony slave > > that's used for reporting queries. The nice thing about this setup is > > you only need to replicate the tables you run reports against. > > > > I would look at fixing the slow queries so that they aren't a problem first.
I'm not sure you're reading the same thread as me. Or something. I've had reporting queries that took the better part of an hour to run, and this was completely normal. When you're running millions of rows against each other for reporting queries it's not unusual to blow out the cache. Maybe the queries are inefficient, and maybe they're not. But one should not be running reporting queries on a live transactional database. > > I'm sure if you send in your queries and table defs you can get some > useful feedback here. > > If there is no way of improving them then look at a reporting slave. > > > -- > > Shane Ambler > pgSQL (at) Sheeky (dot) Biz > > Get Sheeky @ http://Sheeky.Biz > -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
