This can be fixed by patching the default config file

--- /etc/postgresql/8.0/main/postgresql.conf.orig       2005-05-20
07:22:33.000000000 -0500
+++ /etc/postgresql/8.0/main/postgresql.conf    2005-05-20
07:17:26.000000000 -0500
@@ -53,7 +53,7 @@
        # memory per connection slot, in addition to costs from
shared_buffers
        # and max_locks_per_transaction.
 #superuser_reserved_connections = 2
-#unix_socket_directory = ''
+unix_socket_directory = '/var/run/postgresql'
 #unix_socket_group = ''
 #unix_socket_permissions = 0777        # octal
 #rendezvous_name = ''          # defaults to the computer name


The directory will need to be created for it with ownership
postgres:postgres before the daemon starts too. 

maybe a :

mkdir -mode 775  /var/run/postgresql
chown postgres:postgres /var/run/postgresql

... in the post-inst script for postgresql-common


On a related note, have you thought about having a debconf question
about using different ports for v8? It might be very confusing for users
to have 2 different installations on different ports, and I suspect it
will create more problems than it solves.


On Fri, 2005-05-20 at 10:18 -0700, Debian Bug Tracking System wrote:
> Thank you for the problem report you have sent regarding Debian.
> This is an automatically generated reply, to let you know your message has
> been received.  It is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> Your message has been sent to the package maintainer(s):
>  Martin Pitt <[EMAIL PROTECTED]>
> 
> If you wish to submit further information on your problem, please send
> it to [EMAIL PROTECTED] (and *not* to
> [EMAIL PROTECTED]).
> 
> Please do not reply to the address at the top of this message,
> unless you wish to report a problem with the Bug-tracking system.
> 
> Debian bug tracking system administrator
> (administrator, Debian Bugs database)
> 
-- 
David Stanaway <[EMAIL PROTECTED]>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to