On Tue, Mar 28, 2006 at 10:42:13AM -0800, Richard Broersma Jr wrote:
> Could RRS be implemented in a similar fashion to OPC-HDA?
I'm not really familiar with that. The idea behind RRS is that you keep
historical information, but you don't keep the detailed data, similar to
how RRD works.
--
Jim C
Could RRS be implemented in a similar fashion to OPC-HDA?
Regards,
Richard
--- "Jim C. Nasby" <[EMAIL PROTECTED]> wrote:
> On Tue, Mar 28, 2006 at 10:23:45AM -0800, Mark Liberman wrote:
> > > Probably your biggest issue will be temporary files created by temporary
> > > tables, sorts that
> spi
On Tue, Mar 28, 2006 at 10:23:45AM -0800, Mark Liberman wrote:
> > Probably your biggest issue will be temporary files created by temporary
> > tables, sorts that spill to disk, etc.
>
> Is there any way to monitor this so I can estimate?
Keep an eye on $PGDATA/base/{database_oid}/pgsql_tmp.
>
On Tue, 2006-03-28 at 12:23, Mark Liberman wrote:
> > Probably your biggest issue will be temporary files created by
> temporary tables, sorts that spill to disk, etc.
>
> Is there any way to monitor this so I can estimate?
>
> > What I'm confused by is the concern about disk space in the first
>
Title: RE: [ADMIN] Feedback on auto-pruning approach
> Probably your biggest issue will be temporary files created by temporary tables, sorts that spill to disk, etc.
Is there any way to monitor this so I can estimate?
> What I'm confused by is the concern about disk space i
On Mon, Mar 27, 2006 at 06:32:42PM -0800, Mark Liberman wrote:
> So, I have finally complete this auto-pruning solution. It has proven
> effective in keeping the size of the db under whichever threshold I set in an
> unattended fashion.
>
> I have one final question. If my goal is to maximize
Title: RE: [ADMIN] Feedback on auto-pruning approach
So, I have finally complete this auto-pruning solution. It has proven effective in keeping the size of the db under whichever threshold I set in an unattended fashion.
I have one final question. If my goal is to maximize the amount of
"Mark Liberman" <[EMAIL PROTECTED]> writes:
> where c.oid = a.attrelid
> and c.relnamespace = n.oid
> and c.relkind in ('i','r')
> and a.atttypid not in (26,27,28,29)
> group by c.relname) by_table;
> A few notes:
> 1) I have used 32 bytes for the row tuple header overhead and 4 bytes =
> f
