Oliver Jowett [EMAIL PROTECTED] writes:
per my linux/socket.h:
/* Setsockoptions(2) level. Thanks to BSD these must match IPPROTO_xxx */
#define SOL_IP 0
/* #define SOL_ICMP 1 No-no-no! Due to Linux :-) we cannot use
SOL_ICMP=1 */
#define SOL_TCP 6
(I won't get
-Original Message-
From: [EMAIL PROTECTED] on behalf of Steve Atkins
Sent: Sun 7/31/2005 5:35 AM
To: PostgreSQL-development
Subject: Re: [HACKERS] Remote administration functionality
So, while I can see the attraction of being able to futz with the
database security configuration
Bruce Momjian wrote:
I think the group generally would like a
higher-level API that allows something like:
SET GLOBAL log_statement = 'mod';
This is the typical Core point of view. Any function not usable from
psql can't be ok. So until psql isn't enabled to SET GLOBAL, the rest
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: Sun 7/31/2005 4:39 AM
To: Dave Page
Cc: Tom Lane; Magnus Hagander; PostgreSQL-development
Subject: Remote administration functionality
The idea of the patch was to give applications the full unix I/O
Bruce Momjian wrote:
o ...
o recycle log files
o ...
All these items are on the TODO list already.
Didn't find this on the TODO, what does it mean? Is it what
pg_logfile_rotate() does since my very first logger subprocess posts?
Regards,
Andreas
Tom Lane wrote:
Oliver Jowett [EMAIL PROTECTED] writes:
per my linux/socket.h:
/* Setsockoptions(2) level. Thanks to BSD these must match IPPROTO_xxx */
#define SOL_IP 0
/* #define SOL_ICMP 1 No-no-no! Due to Linux :-) we cannot use
SOL_ICMP=1 */
#define SOL_TCP
Andreas Pflug wrote:
Bruce Momjian wrote:
o ...
o recycle log files
o ...
All these items are on the TODO list already.
Didn't find this on the TODO, what does it mean? Is it what
pg_logfile_rotate() does since my very first logger subprocess posts?
Yes, I think
Dave Page wrote:
The idea of the patch was to give applications the full unix I/O
capabilities, allowing them to program these functions into
administration applications. I think the group generally would like a
higher-level API that allows something like:
SET GLOBAL
Bruce,
On 7/31/05 6:58 AM, Bruce Momjian pgman@candle.pha.pa.us wrote:
TODO has:
o Allow pg_hba.conf settings to be controlled via SQL
This would require a new global table that is dumped to flat file
for
use by the postmaster. We do a similar thing for
Dave Page wrote:
The best I have come up with is functions similar to:
SELECT pg_set_hba_line(20, 'hostssl all all 192.168.1.1/32 md5');
SELECT pg_add_hba_line(19, '# Allow global access for Dave''s test
workstation');
SELECT pg_delete_hba_line(24);
However, there are a couple of things
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: Sun 7/31/2005 2:58 PM
To: Dave Page
Cc: Tom Lane; Magnus Hagander; PostgreSQL-development
Subject: Re: [HACKERS] Remote administration functionality
I was thinking of a global table that can be modified with
I've been trying to figure out what to do about pg_dumpall's --clean
option in view of our recent changes. The problem is that pg_dumpall
tries to delete existing users and groups by putting this in its
output script:
DELETE FROM pg_shadow
WHERE usesysid (SELECT datdba FROM
Luke Lonergan wrote:
Bruce,
On 7/31/05 6:58 AM, Bruce Momjian pgman@candle.pha.pa.us wrote:
TODO has:
o Allow pg_hba.conf settings to be controlled via SQL
This would require a new global table that is dumped to flat file
for
use by the postmaster.
Dave Page wrote:
-Original Message- From: Bruce Momjian
[mailto:[EMAIL PROTECTED] Sent: Sun 7/31/2005 2:58 PM To: Dave
Page Cc: Tom Lane; Magnus Hagander; PostgreSQL-development Subject:
Re: [HACKERS] Remote administration functionality
I was thinking of a global table that
Bruce,
On 7/31/05 5:33 PM, Bruce Momjian pgman@candle.pha.pa.us wrote:
Reload of config file and rotate log files were part of the original
patch that I will try to apply. I am not sure how remote restart would
work.
Reload of config, refresh of IPC structures should be equivalent. It all
On 2005-07-31, Oliver Jowett [EMAIL PROTECTED] wrote:
I'm not worried about changing values; I think that representing the
option level as an IP protocol number, in an interface that
encompasses non-IP protocols, is a bad API design decision.
The interpretation of that parameter, if not equal
Andrew - Supernews wrote:
On 2005-07-31, Oliver Jowett [EMAIL PROTECTED] wrote:
I'm not worried about changing values; I think that representing the
option level as an IP protocol number, in an interface that
encompasses non-IP protocols, is a bad API design decision.
The interpretation of
On 2005-08-01, Oliver Jowett [EMAIL PROTECTED] wrote:
There's no dependency on socket PF mentioned there, and the obvious
reading of that text is that a level identifier uniquely identifies
the protocol controlling the option -- so IPPROTO_TCP unambiguously
means the TCP protocol.
You're
Bruce Momjian pgman@candle.pha.pa.us writes:
Luke Lonergan wrote:
Has there been any agreement or a concept for remote reboot?
Reload of config file and rotate log files were part of the original
patch that I will try to apply. I am not sure how remote restart would
work.
Remote reboot to
19 matches
Mail list logo
