On Sep 8, 2010, at 1:39 PM, Joshua J. Kugler wrote:
> If you do a private socket dir, and connect via that, you don't even
> have to listen on a TCP port at all.
Right, but it's hardwired in that the IP port number is used as part of the
domain socket name, and according to Tom also used someho
On Tuesday 07 September 2010, Scott Ribe elucidated thus:
> On Sep 7, 2010, at 7:09 PM, Tom Lane wrote:
> > Personally, though, I think it's easier to change the default port
> > number and not worry about sharing /tmp. Changing the port is a
> > good idea anyway to avoid any possible conflicts on
On Sep 7, 2010, at 7:09 PM, Tom Lane wrote:
> Personally, though, I think it's easier to change the default port
> number and not worry about sharing /tmp. Changing the port is a good
> idea anyway to avoid any possible conflicts on shared memory IDs.
I was planning on changing the default port
John R Pierce writes:
> On 09/07/10 5:24 PM, Joshua J. Kugler wrote:
>>> I'm pretty sure the socket directory is hard coded in the source, I
>>> don't think you can override it even with ./configure
>> postgresql.conf:
>> unix_socket_directory = '/var/run/postgresql'
> for some reason, I'm rem
On Sep 7, 2010, at 6:28 PM, Greg Sabino Mullane wrote:
> Yep, that should do it. I do this all the time for testing
> various programs. Set the socket with pg_ctl -o "-k newsocketdir"
Thanks :-)
--
Scott Ribe
scott_r...@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice
--
On Sep 7, 2010, at 6:30 PM, John R Pierce wrote:
> for some reason, I'm remembering that last time I looked, there were places
> where this value wasn't being used. but then again, maybe I'm thinking of
> something else entirely different and am just confused. wouldn't be the
> first time.
It is defined in postgresql.conf
unix_socket_directory = '/var/run/postgresql'
On Tue, 07 Sep 2010 17:20:24 -0700
John R Pierce wrote:
> On 09/07/10 5:15 PM, Scott Ribe wrote:
> > Assume I want to install an instance of postgres such that it
> > cannot interfere with another install, or even
On 09/07/10 5:24 PM, Joshua J. Kugler wrote:
I'm pretty sure the socket directory is hard coded in the source, I
don't think you can override it even with ./configure
postgresql.conf:
unix_socket_directory = '/var/run/postgresql'
for some reason, I'm remembering that last time I looked, the
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Assume I want to install an instance of postgres such
> that it cannot interfere with another install,
> or even be visible to other apps. Is this all I need to do:
>
> - install pg somewhere within my own directory
> - init the db somewhere
On Tuesday 07 September 2010, John R Pierce elucidated thus:
> On 09/07/10 5:15 PM, Scott Ribe wrote:
> > Assume I want to install an instance of postgres such that it
> > cannot interfere with another install, or even be visible to other
> > apps. Is this all I need to do:
> >
> > - install pg s
On 09/07/10 5:15 PM, Scott Ribe wrote:
Assume I want to install an instance of postgres such that it cannot interfere
with another install, or even be visible to other apps. Is this all I need to
do:
- install pg somewhere within my own directory
- init the db somewhere within my own director
Assume I want to install an instance of postgres such that it cannot interfere
with another install, or even be visible to other apps. Is this all I need to
do:
- install pg somewhere within my own directory
- init the db somewhere within my own directory
- disallow IP connections
- set the sock
12 matches
Mail list logo
