Re: Server instrumentation

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>
Cc: "PostgreSQL-patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Server instrumentation
Date: 2005-06-10 14:23:20
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E490E44B@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

> -----Original Message-----
> From: pgsql-patches-owner(at)postgresql(dot)org
> [mailto:pgsql-patches-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
> Sent: 10 June 2005 14:52
> To: Andreas Pflug
> Cc: PostgreSQL-patches
> Subject: Re: [PATCHES] Server instrumentation
>
>
> > pg_file_stat()
> > pg_file_length()
> > pg_file_read()
> > pg_file_write()
> > pg_file_unlink()
> > pg_file_rename()
> > pg_dir_ls()
>
> I really have serious doubts about the value of this.

They allow superusers to view and modify the server configuration using
tools like pgAdmin or phpPgAdmin. The functionality this allows has been
standard in SQL Server for years and users coming from that platform
that we are now offering an alternative to expect this. It's been a
while, but iirc, DB2 was likewise configurable in this way last time I
used it, and I believe Oracle was as well.

Regards, Dave.

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2005-06-10 15:46:41 Re: psql: customizable readline history filename
Previous Message Andreas Pflug 2005-06-10 14:14:20 Re: Server instrumentation