Add:
> > o Allow pg_hba.conf to specify host names along with IP addresses > > Host name lookup could occur when the postmaster reads the > pg_hba.conf file, or when the backend starts. Another > solution would be to reverse lookup the connection IP and > check that hostname against the host names in pg_hba.conf. > We could also then check that the host name maps to the IP > address.
This commit is contained in:
parent
8325be229c
commit
589b67d34b
11
doc/TODO
11
doc/TODO
@ -2,7 +2,7 @@
|
||||
PostgreSQL TODO List
|
||||
====================
|
||||
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
|
||||
Last updated: Sun Feb 12 14:13:10 EST 2006
|
||||
Last updated: Sun Feb 12 22:42:37 EST 2006
|
||||
|
||||
The most recent version of this document can be viewed at
|
||||
http://www.postgresql.org/docs/faqs.TODO.html.
|
||||
@ -80,6 +80,15 @@ Administration
|
||||
can be inserted between existing rows, e.g. row 2.5 goes
|
||||
between row 2 and row 3.
|
||||
|
||||
o Allow pg_hba.conf to specify host names along with IP addresses
|
||||
|
||||
Host name lookup could occur when the postmaster reads the
|
||||
pg_hba.conf file, or when the backend starts. Another
|
||||
solution would be to reverse lookup the connection IP and
|
||||
check that hostname against the host names in pg_hba.conf.
|
||||
We could also then check that the host name maps to the IP
|
||||
address.
|
||||
|
||||
o %Allow postgresql.conf file values to be changed via an SQL
|
||||
API, perhaps using SET GLOBAL
|
||||
o Allow the server to be stopped/restarted via an SQL API
|
||||
|
@ -8,7 +8,7 @@
|
||||
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
|
||||
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
|
||||
<p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
|
||||
Last updated: Sun Feb 12 14:13:10 EST 2006
|
||||
Last updated: Sun Feb 12 22:42:37 EST 2006
|
||||
</p>
|
||||
<p>The most recent version of this document can be viewed at<br/>
|
||||
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
|
||||
@ -75,6 +75,14 @@ first.
|
||||
The table should have a line number that is a float so rows
|
||||
can be inserted between existing rows, e.g. row 2.5 goes
|
||||
between row 2 and row 3.
|
||||
</p>
|
||||
</li><li>Allow pg_hba.conf to specify host names along with IP addresses
|
||||
<p> Host name lookup could occur when the postmaster reads the
|
||||
pg_hba.conf file, or when the backend starts. Another
|
||||
solution would be to reverse lookup the connection IP and
|
||||
check that hostname against the host names in pg_hba.conf.
|
||||
We could also then check that the host name maps to the IP
|
||||
address.
|
||||
</p>
|
||||
</li><li>%Allow postgresql.conf file values to be changed via an SQL
|
||||
API, perhaps using SET GLOBAL
|
||||
|
Loading…
x
Reference in New Issue
Block a user