"Steinar H. Gunderson" <[EMAIL PROTECTED]> writes:
> On Sat, Dec 11, 2004 at 03:17:13PM +0100, Tomas Skäre wrote:
> > select c.* from cjm_object c
> > inner join
> > (select max(timestamp) as timestamp,objectid,field from cjm_object
> >group by objectid,field) t
> > using(timestamp,object
Hasnul Fadhly bin Hasan wrote:
Hi Bryan,
Just wondering, i ran vacuumdb but didn't get the information that you
get about the free space even when i set the verbose option. How did
you get that?
Thanks,
Hasnul
I believe it is
VACUUM FULL ANALYZE VERBOSE;
At the very end you will get a listing
I tried to subscribe to pgsql-performance, but there seems to be
something wrong with the majordomo, so I'm sending to general too,
where I'm already subscribed.
My problem is this, using PostgreSQL 7.4.6:
I have a table that looks like this:
Table "public.cjm_object"
Column |
Tomas,
> I tried to subscribe to pgsql-performance, but there seems to be
> something wrong with the majordomo, so I'm sending to general too,
> where I'm already subscribed.
Well, I got your e-mail, so obviously you're subscribed to Performance.
> But when doing a search with objectid, class an
I have a question regarding a serious performance hit taken when using a
LIMIT clause. I am using version 7.4.6 on FreeBSD 4.10-STABLE with 2GB
of memory. The table in question contains some 25 million rows with a
bigserial primary key, orderdate index and a referrer index. The 2
select stateme
Thanks for the response.
I just start to get a feel of where TableSpace will be used. You are right I
do not have 7000 logical filesystems.
I am assuming using TableSpace as organization of files in folders in
Windows 2003 Environment. So, each
TableSpace will represent one folder(directory) in a