| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Jim Garrison <jim(dot)garrison(at)nwea(dot)org>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Remote troubleshooting session connection? |
| Date: | 2014-04-04 22:46:45 |
| Message-ID: | 533F3655.3090005@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 04/04/2014 03:41 PM, Jim Garrison wrote:
> I'm working on an ETL system that is driven from Java/JDBC but is implemented mostly as SQL queries against a PostgreSQL database.
>
> An ETL "job" runs inside its own transaction and consists of a series of queries that transform the data from staging tables to the destination tables. If a failure occurs, the transaction rolls back so there's no "debris" left over -- which makes troubleshooting very difficult.
Why not crank up the logging in postgresql.conf and then look at the
postgres logs?
>
> In the Java world we have JPDA, which allows us to connect to a running JVM to examine the state of variables and set breakpoints, etc.
>
> Assuming I can pause the driving Java code between queries in a job, is there any way to connect from PGAdmin (or another tool) and view the state of tables in the in-progress transaction? If this is not currently possible, how difficult would it be to do?
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2014-04-04 22:56:51 | Re: Remote troubleshooting session connection? |
| Previous Message | Jim Garrison | 2014-04-04 22:41:28 | Remote troubleshooting session connection? |