Thread: PG Admin 4
I'm relatively new to PostgreSql and am trying to navigate my way around the tools like PG Admin 4 to do Database Admin work. I'm trying to run an entire set of DDL with lots of tables, indexes, etc. through PG Admin 4 for a database. The only thing I saw after I ran the script was a message about the final index being created and how long the entire script ran in milliseconds. When running a large batch of objects, I would expect to see messages about the result of each individual object being created (like what happens in SSMS for SQL Server, or any of the tools for Oracle). Is there some setting or switch somewhere in PG Admin 4 that I can turn on to see messages for each object that it processes while it is executing my script? It doesn't give me a warm a fuzzy feeling to not see anything while the script it running. Thanks - RW -- Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
On 7/10/20 9:53 AM, rwest wrote: > I'm relatively new to PostgreSql and am trying to navigate my way around the > tools like PG Admin 4 to do Database Admin work. > > I'm trying to run an entire set of DDL with lots of tables, indexes, etc. > through PG Admin 4 for a database. The only thing I saw after I ran the > script was a message about the final index being created and how long the > entire script ran in milliseconds. When running a large batch of objects, I > would expect to see messages about the result of each individual object > being created (like what happens in SSMS for SQL Server, or any of the tools > for Oracle). Is there some setting or switch somewhere in PG Admin 4 that I > can turn on to see messages for each object that it processes while it is > executing my script? It doesn't give me a warm a fuzzy feeling to not see > anything while the script it running. > > Thanks - RW > > > > -- > Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html > > What environment are you in, OS-wise? A shell of some sort to run those scripts is likely your best bet.
Ah, sorry that i didn't specify. I'm running on a Windows platform. We're trying to avoid running in a command-line mode if possible, and leverage the options PG Admin 4 has available to us. Just find it odd that it doesn't report out each Create or Alter statement as it executes the script. -- Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
Oh sorry, should have specified that. We're running on a Windows platform. We're trying to avoid running anything command-line when doing DDL releases and leverage whatever PG Admin 4 can provide us. I'm just wondering why we don't see the results of each CREATE or ALTER statement as the script runs in the tool. That seems very strange to me. Is there some sort of setting or parameter that can force the tool to do this for us? -- Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
On 7/10/20 8:53 AM, rwest wrote: > I'm relatively new to PostgreSql and am trying to navigate my way around the > tools like PG Admin 4 to do Database Admin work. > > I'm trying to run an entire set of DDL with lots of tables, indexes, etc. > through PG Admin 4 for a database. The only thing I saw after I ran the > script was a message about the final index being created and how long the > entire script ran in milliseconds. When running a large batch of objects, I > would expect to see messages about the result of each individual object > being created (like what happens in SSMS for SQL Server, or any of the tools > for Oracle). Is there some setting or switch somewhere in PG Admin 4 that I > can turn on to see messages for each object that it processes while it is > executing my script? It doesn't give me a warm a fuzzy feeling to not see > anything while the script it running. Have you looked in the Query History tab?: https://www.pgadmin.org/docs/pgadmin4/4.23/query_tool.html#query-history-panel > > Thanks - RW > > > > -- > Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html > > -- Adrian Klaver adrian.klaver@aklaver.com
Yes...all that is in there is the same results for the entire batch......no intermediate results for each piece of DDL. I'm submitting a large series of DDL changes in one batch....I'm still looking how to see the results of the execution ofeach DDL statement. RW -----Original Message----- From: Adrian Klaver <adrian.klaver@aklaver.com> Sent: Friday, July 10, 2020 1:47 PM To: Robert West <rwest@gentax.com>; pgsql-general@postgresql.org Subject: Re: PG Admin 4 ATTENTION: This email was sent from an external source. Please exercise caution when opening attachments or clicking links. On 7/10/20 8:53 AM, rwest wrote: > I'm relatively new to PostgreSql and am trying to navigate my way > around the tools like PG Admin 4 to do Database Admin work. > > I'm trying to run an entire set of DDL with lots of tables, indexes, etc. > through PG Admin 4 for a database. The only thing I saw after I ran > the script was a message about the final index being created and how > long the entire script ran in milliseconds. When running a large > batch of objects, I would expect to see messages about the result of > each individual object being created (like what happens in SSMS for > SQL Server, or any of the tools for Oracle). Is there some setting or > switch somewhere in PG Admin 4 that I can turn on to see messages for > each object that it processes while it is executing my script? It > doesn't give me a warm a fuzzy feeling to not see anything while the script it running. Have you looked in the Query History tab?: https://www.pgadmin.org/docs/pgadmin4/4.23/query_tool.html#query-history-panel > > Thanks - RW > > > > -- > Sent from: > https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html > > -- Adrian Klaver adrian.klaver@aklaver.com
Why would you shun the ease of command line batch control?
IT Director
Direct: +44 (0)1376 504510 | Mobile: +44 (0)7887 563420
Oh sorry, should have specified that. We're running on a Windows platform. We're trying to avoid running anything command-line when doing DDL releases and leverage whatever PG Admin 4 can provide us. I'm just wondering why we don't see the results of each CREATE or ALTER statement as the script runs in the tool. That seems very strange to me. Is there some sort of setting or parameter that can force the tool to do this for us? -- Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
Telephone: Witham: +44(0)1376 503500 | London: +44 (0)20 3009 0853 | Frankfurt: +49 (0)69 7191 6000 | Hong Kong: +852 5803 1687 | Toronto: +1 647 503 2848
Web: https://www.manifest.co.uk/
Minerva Analytics Ltd - A Solactive Company
9 Freebournes Court | Newland Street | Witham | Essex | CM8 2BL | United Kingdom
Copyright: This e-mail may contain confidential or legally privileged information. If you are not the named addressee you must not use or disclose such information, instead please report it to admin@minerva.info
Legal: Minerva Analytics is the trading name of: Minerva Analytics Ltd: Registered in England Number 11260966 & The Manifest Voting Agency Ltd: Registered in England Number 2920820 Registered Office at above address. Please Click Here https://www.manifest.co.uk/legal/ for further information.
On 7/10/20 12:54 PM, Robert West wrote: > Yes...all that is in there is the same results for the entire batch......no intermediate results for each piece of DDL. Hmm, that is something you might have to ask here: https://www.pgadmin.org/support/list/ > > I'm submitting a large series of DDL changes in one batch....I'm still looking how to see the results of the execution of each DDL statement. On Unixen I would say tail the log file, not sure how that works in Windows. > > RW > -- Adrian Klaver adrian.klaver@aklaver.com
I gave up on PGAdmin4 and went back to PGAdmin3, although 3 is deprecated now. The History tab will show you what you want after executing a SQL statement.
I don't use Windows any more than I have to but when I did try PGAdmin4 on windows, the feedback was sometimes there and sometimes not. Linux works better.
That said, I agree that executing a script from a command line is the best approach for implementing DDL statements. You can capture the script and the output for further confirmation of success or failure.
Sue
---
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Susan E Hurst Principal Consultant Brookhurst Data LLC Email: susan.hurst@brookhurstdata.com Mobile: 314-486-3261
On 2020-07-10 15:20, Tim Clarke wrote:
Why would you shun the ease of command line batch control?
Tim Clarke MBCS
IT Director
Direct: +44 (0)1376 504510 | Mobile: +44 (0)7887 563420On 10/07/2020 17:36, rwest wrote:Oh sorry, should have specified that. We're running on a Windows platform. We're trying to avoid running anything command-line when doing DDL releases and leverage whatever PG Admin 4 can provide us. I'm just wondering why we don't see the results of each CREATE or ALTER statement as the script runs in the tool. That seems very strange to me. Is there some sort of setting or parameter that can force the tool to do this for us? -- Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
Telephone: Witham: +44(0)1376 503500 | London: +44 (0)20 3009 0853 | Frankfurt: +49 (0)69 7191 6000 | Hong Kong: +852 5803 1687 | Toronto: +1 647 503 2848
Web: https://www.manifest.co.uk/
Minerva Analytics Ltd - A Solactive Company
9 Freebournes Court | Newland Street | Witham | Essex | CM8 2BL | United Kingdom
Copyright: This e-mail may contain confidential or legally privileged information. If you are not the named addressee you must not use or disclose such information, instead please report it to admin@minerva.info
Legal: Minerva Analytics is the trading name of: Minerva Analytics Ltd: Registered in England Number 11260966 & The Manifest Voting Agency Ltd: Registered in England Number 2920820 Registered Office at above address. Please Click Here https://www.manifest.co.uk/legal/ for further information.
I gave up on PGAdmin4 and went back to PGAdmin3, although 3 is deprecated now. The History tab will show you what you want after executing a SQL statement.
I don't use Windows any more than I have to but when I did try PGAdmin4 on windows, the feedback was sometimes there and sometimes not. Linux works better.
That said, I agree that executing a script from a command line is the best approach for implementing DDL statements. You can capture the script and the output for further confirmation of success or failure.
Sue
---
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Susan E Hurst Principal Consultant Brookhurst Data LLC Email: susan.hurst@brookhurstdata.com Mobile: 314-486-3261On 2020-07-10 15:20, Tim Clarke wrote:
Why would you shun the ease of command line batch control?
Tim Clarke MBCS
IT Director
Direct: +44 (0)1376 504510 | Mobile: +44 (0)7887 563420On 10/07/2020 17:36, rwest wrote:Oh sorry, should have specified that. We're running on a Windows platform. We're trying to avoid running anything command-line when doing DDL releases and leverage whatever PG Admin 4 can provide us. I'm just wondering why we don't see the results of each CREATE or ALTER statement as the script runs in the tool. That seems very strange to me. Is there some sort of setting or parameter that can force the tool to do this for us? -- Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
Telephone: Witham: +44(0)1376 503500 | London: +44 (0)20 3009 0853 | Frankfurt: +49 (0)69 7191 6000 | Hong Kong: +852 5803 1687 | Toronto: +1 647 503 2848
Web: https://www.manifest.co.uk/
Minerva Analytics Ltd - A Solactive Company
9 Freebournes Court | Newland Street | Witham | Essex | CM8 2BL | United Kingdom
Copyright: This e-mail may contain confidential or legally privileged information. If you are not the named addressee you must not use or disclose such information, instead please report it to admin@minerva.info
Legal: Minerva Analytics is the trading name of: Minerva Analytics Ltd: Registered in England Number 11260966 & The Manifest Voting Agency Ltd: Registered in England Number 2920820 Registered Office at above address. Please Click Here https://www.manifest.co.uk/legal/ for further information.