On Wed, 16 Jan 2013 23:42:23 +0100
"T. E. Lawrence" wrote:
>
> On 15.01.2013, at 17:32, Jeff Janes wrote:
> > T.E., Fortunately in point releases from August 2012 (9.0.9, 9.1.5,
> > etc.), the default server log settings will log both the cancel and
> > the command triggering the cancel. So if
On 15.01.2013, at 17:32, Jeff Janes wrote:
> T.E., Fortunately in point releases from August 2012 (9.0.9, 9.1.5,
> etc.), the default server log settings will log both the cancel and
> the command triggering the cancel. So if you are running an up to
> date server, you can just look in the logs
On 15.01.2013, at 16:36, Tom Lane wrote:
> "T. E. Lawrence"
> > 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 tha
On Tue, Jan 15, 2013 at 7:36 AM, Tom Lane wrote:
> "T. E. Lawrence"
> writes:
>> On 15.01.2013, at 05:45, Jeff Janes wrote:
Is the autovacuum 100% reliable in relation to VACUUM ANALYZE?
>
>>> No. For example, if you constantly do things that need an access exclusive
>>> lock, then auto
"T. E. Lawrence"
writes:
> On 15.01.2013, at 05:45, Jeff Janes wrote:
>>> Is the autovacuum 100% reliable in relation to VACUUM ANALYZE?
>> No. For example, if you constantly do things that need an access exclusive
>> lock, then autovac will keep getting interrupted and never finish.
> I se
On 15.01.2013, at 05:45, Jeff Janes wrote:
>> Which makes me think that, as we grew the database more than 250 times in
>> size over a 2-3 months period, relying on autovacuum (some tables grew from
>> 200k to 50m records, other from 1m to 500m records), the autovacuum has
>> either let us do
On Monday, January 14, 2013, T. E. Lawrence wrote:
> RESOLVED
> --
> Dear all,
>
> Thank you for your great help and multiple advices.
>
> I discovered the problem and I have to say that it is very stupid and
> strange.
>
> Here is what happened.
>
>
...
> So I decided to try the whole thing pro
RESOLVED
--
Dear all,
Thank you for your great help and multiple advices.
I discovered the problem and I have to say that it is very stupid and strange.
Here is what happened.
>From all advices I tried first partial index. The index was built and there
>was no change in the speed of the slow q
