On Thu, May 10, 2012 at 9:42 AM, Guy Helmer
wrote:
> On May 10, 2012, at 4:31 AM, Horaci Macias wrote:
>
>> Hi everybody,
>>
>> I'm running postgres 9.1 and having disk space problems.
>> My application captures information 24x7 and stores it into the database.
>> This includes several bytea and
thanks Laurenz, at least this confirms the big size is not an issue.
Regarding % of dead tuples vs live tuples, I haven't tried it but
apparently pgstattuple, from contribs should do that, just in case
anybody reading had the same question.
thanks,
H
On 16/05/12 14:41, Albe Laurenz wrote:
Horaci Macias wrote:
> after tuning the autovacuum settings I can now see the tables vaccumed
> and the number of dead tuples dropping whenever an autovacuum happens,
> which makes sense.
Great.
> What I don't see though is the size of the tables ever decreasing, but
> I'm not sure I should see t
after tuning the autovacuum settings I can now see the tables vaccumed
and the number of dead tuples dropping whenever an autovacuum happens,
which makes sense.
What I don't see though is the size of the tables ever decreasing, but
I'm not sure I should see this.
Can somebody please confirm wh
oh I see what you mean; I definitely didn't know that, and makes this
approach much more interesting now :)
thanks,
H
On 10/05/12 19:28, Guy Helmer wrote:
BTW, it's not a problem to query data across multiple days as long as you query
from the parent table -- Postgresql will use the child ta
On May 10, 2012, at 4:31 AM, Horaci Macias wrote:
> Hi everybody,
>
> I'm running postgres 9.1 and having disk space problems.
> My application captures information 24x7 and stores it into the database.
> This includes several bytea and can be ~5M entries a day, so the size can be
> an issue af
BTW, it's not a problem to query data across multiple days as long as you query
from the parent table -- Postgresql will use the child table constraints to
search all the child tables that could contain data.
Guy
On May 10, 2012, at 11:01 AM, Horaci Macias wrote:
> thanks Guy. I had thought ab
thanks Guy. I had thought about using per-day tables (although I didn't
know about child tables) but my problem is that some entries are related
and they can span several minutes, so my worry is that I end up not
finding all the right entries when I search for entries that happen
close to the e
thanks Laurenz, I'll keep an eye on pg_stat_all_tables. I checked just
now and apparently autovacuum has been ran, but this is after my recent
upgrade to 9.1 from 8.3 (I upgraded hoping this problem would go away
and so far the application hasn't been running for long enough for me to
confirm w
Horaci Macias wrote:
> I'm running postgres 9.1 and having disk space problems.
> My application captures information 24x7 and stores it into the
> database. This includes several bytea and can be ~5M entries a day, so
> the size can be an issue after several days.
> My application also cleans up e
Hi everybody,
I'm running postgres 9.1 and having disk space problems.
My application captures information 24x7 and stores it into the
database. This includes several bytea and can be ~5M entries a day, so
the size can be an issue after several days.
My application also cleans up entries older
11 matches
Mail list logo
