| From: | Robert Klemme <shortcutter(at)googlemail(dot)com> |
|---|---|
| To: | Dave Johansen <davejohansen(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Pushing LIMIT into sub-queries of a UNION ALL? |
| Date: | 2011-05-23 19:47:18 |
| Message-ID: | BANLkTimYit+UyPjN0TJKenB7iMx5+uojGQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, May 23, 2011 at 5:54 PM, Dave Johansen <davejohansen(at)gmail(dot)com> wrote:
> I apologize for the multiple posts. I sent this email right after joining
> the list and after it hadn't shown up a day later I figured that it had been
> lost or something and sent the other one.
Sorry for the nitpicking but I even see _three_ instances of this
posting (first on May 18th).
> Also, the database I posted this about does not have internet access and so
> I'm working on getting it moved over to a machine that does or getting it
> the info onto a machine where I can post the pertinent information about the
> schema and explain outputs.
Great!
Cheers
robert
--
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anibal David Acosta | 2011-05-23 21:30:34 | postgres not use index, IN statement |
| Previous Message | Tomas Vondra | 2011-05-23 19:17:33 | Re: Performance degradation of inserts when database size grows |