From: | Joey Quinn <bjquinniii(at)gmail(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: tracking scripts... |
Date: | 2013-11-26 19:45:16 |
Message-ID: | CAG5XHYkHJ3kiZhHBGnPxr8Ugx07UE+Vny922b9i93N1Xw01afQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Sounds like I will have to get comfortable with the command line version of
things... sigh... hate that.
Would that command be from within the psql SQL Shell that came as part of
the install? (I'm living in Windows land).
(and thank-you for the command)
On Tue, Nov 26, 2013 at 1:24 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 11/26/2013 9:24 AM, Joey Quinn wrote:
>
>> When I ran that command (select * from pg_stat_activity"), it returned
>> the first six lines of the scripts. I'm fairly sure it has gotten a bit
>> beyond that (been running over 24 hours now, and the size has increased
>> about 300 GB). Am I missing something for it to tell me what the last line
>> processed was?
>>
>
> that means your GUI lobbed the entire file at postgres in a single PQexec
> call, so its all being executed as a single statement.
>
> psql -f "filename.sql" dbname would have processed the queries one at a
> time.
>
>
> --
> john r pierce 37N 122W
> somewhere on the middle of the left coast
>
>
>
> --
> 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 | Joey Quinn | 2013-11-26 19:48:48 | Re: tracking scripts... |
Previous Message | David Rysdam | 2013-11-26 19:43:42 | having difficulty with explain analyze output |