> -----Original Message-----
> From: Bruce Momjian [mailto:[EMAIL PROTECTED] 
> Sent: 22 June 2005 04:08
> To: Andreas Pflug
> Cc: Dave Page; PostgreSQL-development
> Subject: Re: Server instrumentation patch
> 
> > > The move of dbsize into the backend is similar.  He moves 
> the parts of
> > > dbsize the pgadmin needs into the backend, but makes no mention or
> > > change to /contrib/dbsize to adjust it to the movement of 
> the code. He
> > > has since posted and updated version that fixes this, I think, but
> > > again, we have to discuss how this is to be done --- do 
> we move all the
> > > dbsize functions into the backend, some, or none?  Do the 
> other dbsize
> > > functions stay in /contrib or get deleted?
> > > This needs discussion, not a patch.  And because there are so many
> > > assumptions made in the patch, the patch committers look 
> unreasonable
> > > asking for X changes to his patch, when in fact he made X 
> assumptions in
> > > the patch and never asked anyone before developing the 
> patch about those
> > > assumptions.
> > 
> > This was discussed lengthy starting May 11th, except for the broken 
> > dbsize functions. My post is the result from that.
> 
> Really?  Where?  I don't remember anything about it.

I imagine that would be this lengthy thread:
http://archives.postgresql.org/pgsql-hackers/2005-05/msg00837.php

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to [EMAIL PROTECTED] so that your
       message can get through to the mailing list cleanly

Reply via email to