Обсуждение: Re: Tablespace patch review
> -----Original Message----- > From: pgsql-patches-owner@postgresql.org on behalf of Bruce Momjian > Sent: Sat 6/19/2004 1:05 AM > To: Andreas Pflug > Cc: Tom Lane; Gavin Sherry; PostgreSQL-patches > Subject: Re: [PATCHES] Tablespace patch review > > We can build a gui on top of the command-line tool, no? No, we can't. Don't forget, everything we do in pgAdmin is via libpq. Regards, Dave
Dave Page wrote: >-----Original Message----- >From: pgsql-patches-owner@postgresql.org on behalf of Bruce Momjian >Sent: Sat 6/19/2004 1:05 AM >To: Andreas Pflug >Cc: Tom Lane; Gavin Sherry; PostgreSQL-patches >Subject: Re: [PATCHES] Tablespace patch review > >We can build a gui on top of the command-line tool, no? > > > >No, we can't. Don't forget, everything we do in pgAdmin is via libpq. > > Yeah, gui on top of cmd line is nasty and a pain in regarding portability. It's not exactly challenging to implement it directly either, that's what I'll do in absence of a serverside solution. I'll redirect all pgadmin user speed complaints about this to Toms personal mailbox ;-) Regards, Andreas
Andreas Pflug wrote: > Dave Page wrote: > > >-----Original Message----- > >From: pgsql-patches-owner@postgresql.org on behalf of Bruce Momjian > >Sent: Sat 6/19/2004 1:05 AM > >To: Andreas Pflug > >Cc: Tom Lane; Gavin Sherry; PostgreSQL-patches > >Subject: Re: [PATCHES] Tablespace patch review > > > >We can build a gui on top of the command-line tool, no? > > > > > > > >No, we can't. Don't forget, everything we do in pgAdmin is via libpq. > > > > > Yeah, gui on top of cmd line is nasty and a pain in regarding > portability. It's not exactly challenging to implement it directly > either, that's what I'll do in absence of a serverside solution. I'll > redirect all pgadmin user speed complaints about this to Toms personal > mailbox ;-) I don't see why an admin tool can't connect to each database and get a listing of what is in each tablespace. I don't think connecting to 100 databases to get that information will be slow. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
Bruce Momjian wrote: > > >I don't see why an admin tool can't connect to each database and get a >listing of what is in each tablespace. I don't think connecting to 100 >databases to get that information will be slow. > > > Well, whatever you call slow or not slow. I checked it; connecting 10 databases, retrieving tablespace dependencies (pg_class union pg_schema) and closing takes about one second over an ssl connection, 0.2 seconds with non-ssl. This was a trusted connection, can't check what will happen with md5, krb or so. Regards, Andreas
> -----Original Message----- > From: Andreas Pflug [mailto:pgadmin@pse-consulting.de] > Sent: Sat 6/19/2004 6:40 PM > To: Bruce Momjian > Cc: Dave Page; Tom Lane; PostgreSQL-patches > Subject: Re: [PATCHES] Tablespace patch review > > Well, whatever you call slow or not slow. > I checked it; connecting 10 databases, retrieving tablespace > dependencies (pg_class union pg_schema) and closing takes about one > second over an ssl connection, 0.2 seconds with non-ssl. This was a > trusted connection, can't check what will happen with md5, krb or so. Don't suppose you happened to try it on Win32 did you? Regards, Dave
Dave Page wrote: > > > >>-----Original Message----- >>From: Andreas Pflug [mailto:pgadmin@pse-consulting.de] >>Sent: Sat 6/19/2004 6:40 PM >>To: Bruce Momjian >>Cc: Dave Page; Tom Lane; PostgreSQL-patches >>Subject: Re: [PATCHES] Tablespace patch review >> >>Well, whatever you call slow or not slow. >>I checked it; connecting 10 databases, retrieving tablespace >>dependencies (pg_class union pg_schema) and closing takes about one >>second over an ssl connection, 0.2 seconds with non-ssl. This was a >>trusted connection, can't check what will happen with md5, krb or so. >> >> > >Don't suppose you happened to try it on Win32 did you? > > This was from a win32 workstation (pgadmin3) to a Linux server. Regards, Andreas
Andreas Pflug wrote: > Bruce Momjian wrote: > > > > > > >I don't see why an admin tool can't connect to each database and get a > >listing of what is in each tablespace. I don't think connecting to 100 > >databases to get that information will be slow. > > > > > > > Well, whatever you call slow or not slow. > I checked it; connecting 10 databases, retrieving tablespace > dependencies (pg_class union pg_schema) and closing takes about one > second over an ssl connection, 0.2 seconds with non-ssl. This was a > trusted connection, can't check what will happen with md5, krb or so. Well, we could use something like dbsize to report how much disk space is used by each database in the tablespace (it does an 'ls' in the directory as a server-side function), and connect to the database to get actual table names. I can't think of any clean system that would allow access to the table names in other databases without connecting to them. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073