Re: [HACKERS] For review: Server instrumentation patch - Mailing list pgsql-patches

From Dave Page
Subject Re: [HACKERS] For review: Server instrumentation patch
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC969C@ratbert.vale-housing.co.uk
Whole thread Raw
Responses Re: [HACKERS] For review: Server instrumentation patch
List pgsql-patches

> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin@pse-consulting.de]
> Sent: 01 August 2005 15:05
> To: Dave Page
> Cc: Bruce Momjian; PostgreSQL-patches
> Subject: Re: [PATCHES] [HACKERS] For review: Server
> instrumentation patch
>
> Dave Page wrote:
>
> >>
> >>pg_dir_ls isn't necessary for reading the logfiles;
> >>pg_logdir_ls will do
> >>this.
> >
> >
> > Err, yes, sorry - that was a thinko.
>
> The list isn't complete. pgadmin uses these three functions
> for logfile
> tracking:
>
> - pg_logdir_ls to list logfiles
> - pg_file_length to check for changes of the current logfile
> - pg_file_read to retrieve a logfile

Yes you're right, I didn't check thoroughly (in my defence, the coffee
machine broke this morning). Anyhoo, pg_file_stat is used by
pg_file_length, so that would be required as well.

None of those allow any modification of the filesystem, so do not suffer
the potential security issues that Tom was concerned about, so hopefully
there is no problem with them going in?

Regards, Dave.

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: per user/database connections limit again
Next
From: Tom Lane
Date:
Subject: Re: per user/database connections limit again