Alvaro Herrera <[EMAIL PROTECTED]> writes:
> On Wed, Sep 29, 2004 at 11:23:52PM -0600, Ed L. wrote:
>> On Wednesday September 29 2004 5:17, Tom Lane wrote:
>>> 2004-09-29 18:14:53.621 [520]ERROR: Memory exhausted in
>>> AllocSetAlloc(1189)
>>>
>>> Analyze: 132263832 total in 27 blocks; 2984 f
On Wed, Sep 29, 2004 at 11:23:52PM -0600, Ed L. wrote:
> On Wednesday September 29 2004 5:17, Tom Lane wrote:
> > >
> > > 2004-09-29 18:14:53.621 [520]ERROR: Memory exhausted in
> > > AllocSetAlloc(1189)
> > >
> > > Analyze: 132263832 total in 27 blocks; 2984 free (35 chunks); 132260848
> > >
On Wednesday September 29 2004 5:17, Tom Lane wrote:
> >
> > 2004-09-29 18:14:53.621 [520]ERROR: Memory exhausted in
> > AllocSetAlloc(1189)
> >
> > Analyze: 132263832 total in 27 blocks; 2984 free (35 chunks); 132260848
> > used
>
> Either increase your per-process memory limit, or reduce the
Hi All,
Please let me know how do I unsbscribe to this newsgroup?
Thanks,
Murali
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ed L.
Sent: Wednesday, September 29, 2004 9:21 PM
To: Tom Lane
Cc: [EMAIL PROTECTED]
Subject: Re: [GENERAL] 7.3.4 vacuum
"Ed L." <[EMAIL PROTECTED]> writes:
> On Wednesday September 29 2004 10:18, Tom Lane wrote:
> $ psql -c "show default_statistics_target;"
> default_statistics_target
> ---
> 1000
> (1 row)
> Does that look like its been changed?
Uh ... the default is 10.
On Wednesday September 29 2004 10:18, Tom Lane wrote:
> > Honestly, I don't even know how. How can I check its value to see if
> > someone else has?
>
> show default_statistics_target;
Let me add this: I'm seeing this error show up across multiple clusters,
maybe 5 or 6, all with similar schema
On Wednesday September 29 2004 10:18, Tom Lane wrote:
> > Honestly, I don't even know how. How can I check its value to see if
> > someone else has?
$ psql -c "show default_statistics_target;"
default_statistics_target
---
1000
(1 row)
Does that look like i
> Honestly, I don't even know how. How can I check its value to see if
> someone else has?
show default_statistics_target;
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Wednesday September 29 2004 9:54, Tom Lane wrote:
> You sure you haven't changed default_statistics_target?
Honestly, I don't even know how. How can I check its value to see if
someone else has? What I *do* do is to enable the stats_* stuff in
postgresql.conf, but that's it.
> I'd think
"Ed L." <[EMAIL PROTECTED]> writes:
> The table has 3 columns, one of which contains huge text values. Yes, barf.
That shouldn't matter --- ANALYZE actually deliberately ignores
very-wide values so as not to run out of memory.
You sure you haven't changed default_statistics_target?
I'd think yo
On Wednesday September 29 2004 8:59, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> >> Either increase your per-process memory limit, or reduce the
> >> statistics targets for this table ...
> >
> > What am I missing?
> >
> > $ ulimit -a
> > time(seconds)unlimited
> > file(blocks)
"Ed L." <[EMAIL PROTECTED]> writes:
>> Either increase your per-process memory limit, or reduce the statistics
>> targets for this table ...
> What am I missing?
> $ ulimit -a
> time(seconds)unlimited
> file(blocks) unlimited
> data(kbytes) 131072
^^^
On Wednesday September 29 2004 8:33, Ed L. wrote:
> On Wednesday September 29 2004 5:17, Tom Lane wrote:
> > "Ed L." <[EMAIL PROTECTED]> writes:
> > > I'm getting a slew of these repeatable errors when running ANALYZE
> > > and/or VACUUM ANALYZE (from an autovacuum process) against a
> > > 7.3.4 cl
On Wednesday September 29 2004 5:17, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > I'm getting a slew of these repeatable errors when running ANALYZE
> > and/or VACUUM ANALYZE (from an autovacuum process) against a
> > 7.3.4 cluster on HP-UX B.11.00:
> >
> > 2004-09-29 18:14:53.621 [520
"Ed L." <[EMAIL PROTECTED]> writes:
> I'm getting a slew of these repeatable errors when running ANALYZE
> and/or VACUUM ANALYZE (from an autovacuum process) against a
> 7.3.4 cluster on HP-UX B.11.00:
> 2004-09-29 18:14:53.621 [520]ERROR: Memory exhausted in AllocSetAlloc(1189)
> Analyze:
I'm getting a slew of these repeatable errors when running ANALYZE
and/or VACUUM ANALYZE (from an autovacuum process) against a
7.3.4 cluster on HP-UX B.11.00:
2004-09-29 18:14:53.621 [520]ERROR: Memory exhausted in AllocSetAlloc(1189)
This error is in the FAQ, but that answer does not ap
16 matches
Mail list logo
