Lists: | pgsql-novice |
---|
From: | "Devinder K Rajput" <Devinder(dot)Rajput(at)ipaper(dot)com> |
---|---|
To: | "Graham Bartlett" <gbartlett(at)gamet(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org, pgsql-novice-owner(at)postgresql(dot)org |
Subject: | Re: Problem connecting to postgres |
Date: | 2002-12-11 19:55:45 |
Message-ID: | OF8735289E.59610F5A-ON86256C8C.006CEA90@ipaper.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-novice |
If you are on 7.3x, this should work:
host all all trust
host all all 127.0.0.1 255.255.255.255 trust
host all all 10.1.1.0 255.255.255.0 trust
on earlier versions:
host all trust
host all 127.0.0.1 255.255.255.255 trust
host all 10.1.1.0 255.255.255.0 trust
hth,
Devinder
"Graham Bartlett"
<gbartlett(at)gamet(dot)com> To: pgsql-novice(at)postgresql(dot)org
Sent by: cc:
pgsql-novice-owner(at)pos Subject: [NOVICE] Problem connecting to postgres
tgresql.org
12/11/2002 01:37 PM
After installing Postgres I tried to make a connection to the DB. I made
sure to use the '-i' to enable JDBC connection. I'm receiving the
following error:
"No pg_hba.conf entry for host 10.1.1.79, user gpms, database gpms"
I have created the gpms user and gpms database. I can connect to the
database only when I add:
host all 10.1.1.79 255.255.255.255 trust
to the pg_hba.conf file.
I never had to do this before. I simply want to enable all IPs to
connect to the database without specifying every one of those IPs in the
pg_hba.conf file. How do I do this?
Thanks!
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly
From: | "Mel Jamero" <mel(at)gmanmi(dot)tv> |
---|---|
To: | <pgsql-novice(at)postgresql(dot)org>, <pgsql-novice-owner(at)postgresql(dot)org> |
Subject: | Re: NOTICE: can't shrink relation |
Date: | 2002-12-12 14:44:25 |
Message-ID: | 000001c2a1ec$f81625b0$1b06a8c0@mel |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-novice |
hi,
could anyone please give a brief explanation of these notices.. thanks.
NOTICE: Rel pg_type: TID 26/9: InsertTransactionInProgress 18854950 - can't
shrink relation
NOTICE: Rel pg_attribute: TID 345/2: InsertTransactionInProgress 18854950 -
can't shrink relation
NOTICE: Rel pg_attribute: TID 345/3: InsertTransactionInProgress 18854950 -
can't shrink relation
NOTICE: Rel pg_attribute: TID 345/4: InsertTransactionInProgress 18854950 -
can't shrink relation
NOTICE: Rel pg_attribute: TID 345/5: InsertTransactionInProgress 18854950 -
can't shrink relation
NOTICE: Rel pg_attribute: TID 345/6: InsertTransactionInProgress 18854950 -
can't shrink relation
NOTICE: Rel pg_attribute: TID 345/7: InsertTransactionInProgress 18854950 -
can't shrink relation
NOTICE: Rel pg_attribute: TID 345/8: InsertTransactionInProgress 18854950 -
can't shrink relation
NOTICE: Rel pg_attribute: TID 345/9: InsertTransactionInProgress 18854950 -
can't shrink relation
NOTICE: Rel pg_attribute: TID 345/10: InsertTransactionInProgress
18854950 - can't shrink relation
NOTICE: Rel pg_attribute: TID 345/11: InsertTransactionInProgress
18854950 - can't shrink relation
NOTICE: Rel pg_attribute: TID 345/12: InsertTransactionInProgress
18854950 - can't shrink relation
NOTICE: Rel pg_attribute: TID 345/13: InsertTransactionInProgress
18854950 - can't shrink relation
mel
From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | mel(at)gmanmi(dot)tv |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: NOTICE: can't shrink relation |
Date: | 2002-12-12 16:58:31 |
Message-ID: | 19961.1039712311@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-novice |
"Mel Jamero" <mel(at)gmanmi(dot)tv> writes:
> could anyone please give a brief explanation of these notices.. thanks.
> NOTICE: Rel pg_type: TID 26/9: InsertTransactionInProgress 18854950 - can't
> shrink relation
That's just VACUUM being conservative --- it doesn't want to risk moving
tuples when there are open transactions affecting the table. (In this
case I'd guess that you had an uncommitted transaction that created a
table. The rows describing its columns have been added to pg_attribute,
but not committed yet.)
regards, tom lane