From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | <cbbrowne(at)acm(dot)org> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: request for feature: psql 'DSN' option |
Date: | 2006-07-07 10:33:14 |
Message-ID: | 4670.24.211.165.134.1152268394.squirrel@www.dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Christopher Browne said:
> Per tonight's dinner discussion, it Sure Would Be Nice if psql had an
> additional option that allowed passing in a conninfo string.
>
> The notion: Plenty of libraries out there like Pg, DBI::Pg, and such
> make you specify connections in the form:
> "host=my.db.host.example.org port=5678 dbname=dumb_db user=chewie"
>
> Since those strings need to be kept around for the programs that are
> directly using conninfo, it Sure Would Be Nice if those strings could
> also be used as arguments to psql.
>
> Peter Eisentraut observed that "-D" is not yet used; that's certainly
> an option.
>
> Thus, supposing we kept conninfo strings in a series of files in
> /opt/scripts/conninfo, we might run a script via...
>
> #!/bin/sh
> CONNINFO=`cat /opt/scripts/conninfo/dumb_db.conninfo`
> PERIOD='90 days'
> QUERY="delete from my_table where trans_on < now() -
> '${PERIOD}'::interval;" QUERY2="vacuum analyze my_table;"
> psql -D "${CONNINFO}" -c "${QUERY}"
> psql --pqconninfo="${CONNINFO}" -c "${QUERY2}"
>
> I'm not sure those are forcibly the best names for options, but
> they're a thought...
Why is this better than using the service file?
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2006-07-07 11:33:40 | Re: request for feature: psql 'DSN' option |
Previous Message | Diogo Biazus | 2006-07-07 05:35:52 | xlog viewer prototype and new proposal |