| From: | "T(dot) E(dot) Lawrence" <t(dot)e(dot)lawrence(at)icloud(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: reducing number of ANDs speeds up query RESOLVED |
| Date: | 2013-01-16 22:41:12 |
| Message-ID: | 9ECE0FF1-E4D1-417C-AA18-2B3579030568@icloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 15.01.2013, at 16:36, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "T. E. Lawrence" <t(dot)e(dot)lawrence(at)icloud(dot)com> <CAMkU=1y6UuxPYbf_ky8DVDsJi=g=uQ1t0B6kwLEtdc7NLxB_-
>> So, apparently, we need to interrupt the heavy imports on some reasonable intervals and do manual VACUUM ANALYZE?
>
> Data import as such, no matter how "heavy", shouldn't be a problem.
> The question is what are you doing that takes access-exclusive table
> locks frequently, and do you really need to do that?
>
> A quick look at the docs suggests that ALTER TABLE, REINDEX, or CLUSTER
> would be the most likely candidates for taking exclusive table locks.
>
> regards, tom lane
Thank you for this.
We will have to research into this, it will take a while.
T.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | T. E. Lawrence | 2013-01-16 22:42:23 | Re: reducing number of ANDs speeds up query RESOLVED |
| Previous Message | Robert James | 2013-01-16 22:28:41 | argument of AND must not return a set when using regexp_matches |