Is there a way to set the connection timeout using psql cli? How can I set a connection timeout to something low like 3 seconds using the following:
PGPASSWORD=passwordhere psql -h 10.0.0.144 -U myuser -c "select 1" -d mydatabase
As far as I can tell, psql does not support a connection timeout parameter. In the example above 10.0.0.144 is invalid and this command hangs for a long time. I need the command to fail fast if the host is incorrect.
I know I can list the triggers with \dft. But how can I see one concrete trigger? I want to know details like on which events the trigger is executed, which function is executed and so on.
We switched from PostgreSQL 8.3 to 9.0. Perhaps it's a new feature or perhaps just a configuration change, but now when output from commands (like, \d tablename) exceeds visible vertical space, psql seem to pipe the output through something similar to less. I could not find a way to turn this behaviour off. Any advice? Thanks.
P.S. I'm scrolling the buffer using PuTTY's Shift+PgUp/PgDn so I don't need psql's paging. Plus, when I press q in the psql's paging, its output disappears from the screen entirely (just like after running less in bash), which is wrong from the general use-cases point of view.
I want to restore a database of postgreSQL, but before do it i need to empty the restore target database.
Is there an option of psql to do it ?
Now i use a command line as the following :
psql -U postgres db_test < testdb.sql
I am writing a shell script which makes calls to psql using 2 forms... one is by command (-c), the other is by file (-f).
e.g. psql -c "create table foo (bar integer)"
psql -f foobar.sql
One difference between these forms is that a call by command (-c) returns a non-zero exit code if an error is encountered, while a call by file (-f) always seems to return zero.
I'm wondering if there is a workaround for this behaviour? (i.e. return non-zero if an error occurs while executing a file).
Thanks.