From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | psql - better support pipe line |
Date: | 2015-08-24 05:06:25 |
Message-ID: | CAFj8pRBdu3uTC6wJefy5f_qNzn2Dr1ReGwc9Ey_wzVyggWo+rQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
I found so a set "psql" and "xargs" is pretty strong. But I miss a psql
option for simple returning current database and continuing in pipeline.
What I am doing:
psql postgres -At -c "select datname from pg_database" |
xargs -P 3 -I % psql % -At -c "select current_databe() from
pg_stat_all_tables
where relname = 'pg_attribute' and n_dead_tup > 100000" |
xargs -P 3 -I % sh -c "psql % -q -c 'analyze pg_attribute'; echo %" |
xargs -P 3 -I % psql % -At -c "select curren_database() from ..."
it works perfectly - but the line
xargs -P 3 -I % sh -c "psql % -q -c 'analyze pg_attribute'; echo %"
is little bit ugly - with some psql option it can be cleaned to
xargs -P3 -I % psql % -q --echo-db -c "analyze pg_attribute" | ...
--echo-db requires -q option
What are you thinking about this idea?
Regards
Pavel
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kaltenbrunner | 2015-08-24 06:33:24 | Re: (full) Memory context dump considered harmful |
Previous Message | Amit Kapila | 2015-08-24 03:43:09 | Re: checkpointer continuous flushing |