From: | Susan Cassidy <susan(dot)cassidy(at)decisionsciencescorp(dot)com> |
---|---|
To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
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 21:46:41 |
Message-ID: | CAE3Q8okN-toK7iPf=A=i+vXB82=Vcw=WX2ZXF_-4J4+MxCUkww@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I finally figured it out, after changing my code to output the lines per
the number of rows of output, instead of until data[0] was blank. It
turned out that data[0] was sometimes blank, and I forgot about that, and
was stopping the output after I got back an empty record (or so I thought).
So, all my fault.
The syslog thing I fixed by changing log_min_duration to 0, instead of
letting it default. I don't think this used to be the default (to not log
any statements).
Thanks for all the ideas, anyway, folks.
Thanks again,
Susan
On Thu, Mar 13, 2014 at 2:27 PM, Rob Sargent <robjsargent(at)gmail(dot)com> wrote:
> On 03/13/2014 03:23 PM, Susan Cassidy wrote:
>
>> The only one that comes out different is inet_server_addr, via the
>> program, it comes out:
>> ::1
>> whereas via psql it comes out empty.
>>
>> Yes, I am 100% sure I am using the same schema (which I never specify, so
>> I am using 'public') and the same user and database.
>>
>> Susan
>>
>>
>>
>> Unless username is also a schema name, then you're in that schema.
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Konoplev | 2014-03-13 22:12:25 | Re: [BUGS] Very slow query in PostgreSQL 9.3.3 |
Previous Message | Susan Cassidy | 2014-03-13 21:28:19 | Re: puzzling perl DBI vs psql problem |