postgresql.conf listen_address comment clarification

Started by Darcy Buskermolenalmost 21 years ago2 messagespatches
Jump to latest
#1Darcy Buskermolen
darcy@wavefire.com

The term interfaces is a bit ambiguous and unclear that hostname/ipaddresses
are expected and not a physical name (eth0, lo0, fxp0, .....) I hope this
patch clears that up a bit to bring it more in line with the official
documentation.

--
Darcy Buskermolen
Wavefire Technologies Corp.

http://www.wavefire.com
ph: 250.717.0200
fx: 250.763.1759

Attachments:

postgresql.conf.sample.patchtext/x-diff; charset=us-ascii; name=postgresql.conf.sample.patchDownload+3-2
#2Bruce Momjian
bruce@momjian.us
In reply to: Darcy Buskermolen (#1)
Re: postgresql.conf listen_address comment clarification

Thanks, updated.

---------------------------------------------------------------------------

Darcy Buskermolen wrote:

The term interfaces is a bit ambiguous and unclear that hostname/ipaddresses
are expected and not a physical name (eth0, lo0, fxp0, .....) I hope this
patch clears that up a bit to bring it more in line with the official
documentation.

--
Darcy Buskermolen
Wavefire Technologies Corp.

http://www.wavefire.com
ph: 250.717.0200
fx: 250.763.1759

[ Attachment, skipping... ]

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

-- 
  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