From: | Susan Cassidy <susan(dot)cassidy(at)decisionsciencescorp(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: puzzling perl DBI vs psql problem |
Date: | 2014-03-13 20:25:52 |
Message-ID: | CAE3Q8okwDjJd3tA4LMqyKOrmXmOZqCFT9TyiH4a1ZK9n8i-iJA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
No, I am connecting to the right database, as my log info shows. No
duplicate table names, except in different databases. Those tables show
all the data I expect, oddly enough, if I connect the perl program to that
database. It is only this database that is giving me trouble. Which is
another oddity. The identical test database is working fine. Only this
database is giving me trouble. Naturally the "live" database is causing
problems.
Susan
On Thu, Mar 13, 2014 at 12:25 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Susan Cassidy <susan(dot)cassidy(at)decisionsciencescorp(dot)com> writes:
> > I have a weird issue that I can't figure out.
> > If I run the exact same query through psql as through perl DBI, I get
> > different results. I get far fewer results with DBI than through the
> psql
> > command line.
>
> Any possibility that the perl program is connecting to a different
> database, with similar-but-not-identical data in it?
>
> I've seen variants on that theme involving different users with different
> search_path settings finding different-but-similarly-named tables in
> different schemas of the same database.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Atkins | 2014-03-13 20:26:58 | Re: puzzling perl DBI vs psql problem |
Previous Message | Susan Cassidy | 2014-03-13 20:20:53 | Re: puzzling perl DBI vs psql problem |