Re: pg_hba.conf issue

From: "Vishal Arora" <aroravishal22(at)hotmail(dot)com>
To: RKhetan(at)crisil(dot)com, pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_hba.conf issue
Date: 2007-07-03 04:18:30
Message-ID: BAY123-F345204EE0467A6179DBC3BA90C0@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

>From: Ritu Khetan <RKhetan(at)crisil(dot)com>
>To: pgsql-admin(at)postgresql(dot)org
>Subject: [ADMIN] pg_hba.conf issue
>Date: Mon, 2 Jul 2007 18:40:22 +0530
>
>
>Hi friends,
>
>We have a product with Postgres 8.1 integrated for installations on
>Windows. The standard pg_hba.conf configuration going in the package is
>
>
># TYPE DATABASE USER CIDR-ADDRESS METHOD
>
># IPv4 local connections:
>host all all 127.0.0.1/32 trust
># IPv6 local connections:
>#host all all ::1/128 trust
>#host all all 172.21.42.121/24 trust
>host all all 172.21.51.56/24 trust
>
Move your entries from IPv6 to IPv4 block.

>While this works at most of the locations, we have a peculiar error coming
>up at 2-3 locations. The error reads:

>Regards,
>Ritu
>Disclaimer :
>This message (including any attachments) contains confidential information.
>If you are not the intended recipient, please delete the message (including
>any attachments) from your system without using, transmitting or storing
>it. Please also immediately inform the sender. E-mails are not secure and
>may suffer from errors, viruses, unauthorized interceptions / amendments.
>CRISIL and its subsidiaries do not accept any liability for loss or damage
>caused by this e-mail and may monitor e-mail traffic.
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org

_________________________________________________________________
http://liveearth.msn.com

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Vishal Arora 2007-07-03 04:21:41 Re: pg_hba.conf issue
Previous Message Joe Barwell 2007-07-03 01:35:33 problem running postgres server on startup