Sponsored Content
Top Forums Shell Programming and Scripting PSQL multiple queries output to file Post 302994176 by nms on Monday 20th of March 2017 07:00:46 AM
Old 03-20-2017
Hammer & Screwdriver PSQL multiple queries output to file

Hi,

I have a shell script containing multiple PSQL queries for which I want the output to be redirected to a text file.

Code:
psql -U postgres -d database -o textfile.txt << EOF
Query1;
Query2;
Query ....;
EOF

When executing the script, queries outputs are directed to textfile.txt, however when script was set in cron, textfile.txt is not being updated.
Does anyone have a different way how I can output query results to a text file.


Moderator's Comments:
Mod Comment Please use CODE tags as required by forum rules!

Last edited by RudiC; 03-20-2017 at 08:15 AM.. Reason: Added CODE tags.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Run SQL queries in DB2 and output to file

Hi, I new to Unix and scripting. Following is my requirement. Can someone tell me whether its possible or not. Also please let me know how to proceed further if this is possible. List of queries are stored in a file. For example, I have to run a query like this: Select * from &XYZ where... (0 Replies)
Discussion started by: simhasuri
0 Replies

2. Shell Programming and Scripting

Multiple MySql queries in shell script?

Hi guys, i know how to run a single query using mysql embedded in a shell script as follows: `mysql -umyuser -pmypass --host myhost database<<SQL ${query}; quit SQL` However, how would i be able to run several queries within the same connection? The reason for this is i am creating... (3 Replies)
Discussion started by: muay_tb
3 Replies

3. Shell Programming and Scripting

grep -f, how to output failed queries

Hi folks, I've been using grep -f file1 file2 to get lines that match a file1 line from file2. I'm now interested in getting the lines from file1 where there was no match in file2. I believe the -v option will give me unmatched lines from file2, but I'm looking for unmatched lines from... (3 Replies)
Discussion started by: sanjuro
3 Replies

4. Shell Programming and Scripting

psql output without return \n

Hi Everyone, When i finish running # echo `psql -t -U root databaseA -c "select a, b from book"`; i get the output 107275 | 14 107301 | 2 107446 | 6 107820 | 77 107929 | 101 Would like to have the result like: 107275 | 14 107301 | 2 107446 | 6 107820 | 77 107929 | 101 (7 Replies)
Discussion started by: jimmy_y
7 Replies

5. UNIX for Advanced & Expert Users

Connecting once using sqlplus and doing multiple queries

Hello everyone, It's my first week using unix and shell scripting. I tried creating a script that has a function that execute SQL query. my script looks something like this: ---------------------------------------------------- #!/bin/sh tableName="myTable" secondTable="secondTable"... (2 Replies)
Discussion started by: edlin_r
2 Replies

6. UNIX for Dummies Questions & Answers

multiple queries in single sqlplus

I need to connect a databas eusing sqlplus and i need to store the results of each query in separate file. is it possible to achieve this usng single sqlplus? i dont want to connect each time for each query. thanks (3 Replies)
Discussion started by: pandeesh
3 Replies

7. Shell Programming and Scripting

Grep from multiple patterns multiple file multiple output

Hi, I want to grep multiple patterns from multiple files and save to multiple outputs. As of now its outputting all to the same file when I use this command. Input : 108 files to check for 390 patterns to check for. output I need to 108 files with the searched patterns. Xargs -I {} grep... (3 Replies)
Discussion started by: Diya123
3 Replies

8. Shell Programming and Scripting

Help with storing the output of multiple sql queries to a file

Hi All, I have a file queries.txt as follows : SELECT COLUMN1 FROM SCHEMA2.TABLE1 MINUS SELECT COLUMN1 FROM SCDEMA2.TABLE2; SELECT COLUMN2 FROM SCHEMA2.TABLE1 MINUS SELECT COLUMN2 FROM SCDEMA2.TABLE2; SELECT COLUMN3 FROM SCHEMA2.TABLE1 MINUS SELECT COLUMN3 FROM SCDEMA2.TABLE2; SELECT... (2 Replies)
Discussion started by: SriRamKrish
2 Replies

9. Shell Programming and Scripting

Psql output into array and read 2 fields into different variables

Hello Just edited the entry to make it easier to understand what i want How can i achieve this: GOAL: read 2 field from a table with PSQL result of this PSQL command is this INSTALLEDLANG=$(su - postgres -c "psql -A -t -q -c -d ${DBNAME} -t -c 'SELECT code, iso_code from res_lang'") ... (0 Replies)
Discussion started by: winston6071
0 Replies

10. Shell Programming and Scripting

Storing multiple sql queries output into variable by running sql command only once

Hi All, I want to run multiple sql queries and store the data in variable but i want to use sql command only once. Is there a way without running sql command twice and storing.Please advise. Eg : Select 'Query 1 output' from dual; Select 'Query 2 output' from dual; I want to... (3 Replies)
Discussion started by: Rokkesh
3 Replies
PG_CTL(1)						  PostgreSQL Server Applications						 PG_CTL(1)

NAME
       pg_ctl - start, stop, or restart a PostgreSQL server

SYNOPSIS
       pg_ctl start [ -w ]  [ -t seconds ]  [ -s ]  [ -D datadir ]  [ -l filename ]  [ -o options ]  [ -p path ]  [ -c ]

       pg_ctl stop [ -W ]  [ -t seconds ]  [ -s ]  [ -D datadir ]  [ -m
	 [ s[mart] ]  [ f[ast] ]  [ i[mmediate] ]
	]

       pg_ctl restart [ -w ]  [ -t seconds ]  [ -s ]  [ -D datadir ]  [ -c ]  [ -m
	 [ s[mart] ]  [ f[ast] ]  [ i[mmediate] ]
	]  [ -o options ]

       pg_ctl reload [ -s ]  [ -D datadir ]

       pg_ctl status [ -D datadir ]

       pg_ctl kill [ signal_name ]  [ process_id ]

       pg_ctl register [ -N servicename ]  [ -U username ]  [ -P password ]  [ -D datadir ]  [ -w ]  [ -t seconds ]  [ -o options ]

       pg_ctl unregister [ -N servicename ]

DESCRIPTION
       pg_ctl  is  a utility for starting, stopping, or restarting the PostgreSQL backend server (postgres(1)), or displaying the status of a run-
       ning server. Although the server can be started manually, pg_ctl encapsulates tasks such as redirecting log output and  properly  detaching
       from the terminal and process group. It also provides convenient options for controlled shutdown.

       In start mode, a new server is launched. The server is started in the background, and standard input is attached to /dev/null. The standard
       output and standard error are either appended to a log file (if the -l option is used), or redirected  to  pg_ctl's  standard  output  (not
       standard error). If no log file is chosen, the standard output of pg_ctl should be redirected to a file or piped to another process such as
       a log rotating program like rotatelogs; otherwise postgres will write its output to the controlling terminal (from the background) and will
       not leave the shell's process group.

       In  stop  mode,	the  server that is running in the specified data directory is shut down. Three different shutdown methods can be selected
       with the -m option: ``Smart'' mode waits for online backup mode to finish and all the clients to disconnect. This is the default.  ``Fast''
       mode  does  not wait for clients to disconnect and will terminate an online backup in progress. All active transactions are rolled back and
       clients are forcibly disconnected, then the server is shut down. ``Immediate'' mode will abort all server processes without a  clean  shut-
       down. This will lead to a recovery run on restart.

       restart mode effectively executes a stop followed by a start. This allows changing the postgres command-line options.

       reload  mode simply sends the postgres process a SIGHUP signal, causing it to reread its configuration files (postgresql.conf, pg_hba.conf,
       etc.). This allows changing of configuration-file options that do not require a complete restart to take effect.

       status mode checks whether a server is running in the specified data directory. If it is, the PID and the command line  options	that  were
       used to invoke it are displayed.

       kill  mode  allows  you	to send a signal to a specified process. This is particularly valuable for Microsoft Windows which does not have a
       kill command. Use --help to see a list of supported signal names.

       register mode allows you to register a system service on Microsoft Windows.

       unregister mode allows you to unregister a system service on Microsoft Windows, previously registered with the register command.

OPTIONS
       -c     Attempt to allow server crashes to produce core files, on platforms where this available, by lifting any soft resource limit  placed
	      on them.	This is useful in debugging or diagnosing problems by allowing a stack trace to be obtained from a failed server process.

       -D datadir
	      Specifies the file system location of the database files. If this is omitted, the environment variable PGDATA is used.

       -l filename
	      Append  the  server log output to filename. If the file does not exist, it is created. The umask is set to 077, so access to the log
	      file from other users is disallowed by default.

       -m mode
	      Specifies the shutdown mode. mode can be smart, fast, or immediate, or the first letter of one of these three.

       -o options
	      Specifies options to be passed directly to the postgres command.

	      The options are usually surrounded by single or double quotes to ensure that they are passed through as a group.

       -p path
	      Specifies the location of the postgres executable. By default the postgres executable is taken from the same directory as pg_ctl, or
	      failing  that,  the hard-wired installation directory. It is not necessary to use this option unless you are doing something unusual
	      and get errors that the postgres executable was not found.

       -s     Only print errors, no informational messages.

       -t     The number of seconds to wait when waiting for start or shutdown to complete.

       -w     Wait for the start or shutdown to complete. The default wait time is 60 seconds. This is the default option for  shutdowns.  A  suc-
	      cessful  shutdown  is  indicated	by  removal  of the PID file. For starting up, a successful psql -l indicates success. pg_ctl will
	      attempt to use the proper port for psql. If the environment variable PGPORT exists, that is used. Otherwise, it will see if  a  port
	      has  been  set  in the postgresql.conf file.  If neither of those is used, it will use the default port that PostgreSQL was compiled
	      with (5432 by default). When waiting, pg_ctl will return an accurate exit code based on the success of the startup or shutdown.

       -W     Do not wait for start or shutdown to complete. This is the default for starts and restarts.

   OPTIONS FOR WINDOWS
       -N servicename
	      Name of the system service to register. The name will be used as both the service name and the display name.

       -P password
	      Password for the user to start the service.

       -U username
	      User name for the user to start the service. For domain users, use the format DOMAINusername.

ENVIRONMENT
       PGDATA Default data directory location.

       PGPORT Default port for psql(1) (used by the -w option).

       For additional server variables, see postgres(1).  This utility, like most other PostgreSQL utilities, also uses the environment  variables
       supported by libpq (see in the documentation).

FILES
       postmaster.pid
	      The existence of this file in the data directory is used to help pg_ctl determine if the server is currently running or not.

       postmaster.opts
	      If  this	file  exists  in  the  data directory, pg_ctl (in restart mode) will pass the contents of the file as options to postgres,
	      unless overridden by the -o option. The contents of this file are also displayed in status mode.

       postgresql.conf
	      This file, located in the data directory, is parsed to find the proper port to use with psql when the -w is given in start mode.

NOTES
       Waiting for complete start is not a well-defined operation and might fail if access control is set up so that a local client cannot connect
       without	manual	interaction  (e.g., password authentication). For additional connection variables, see in the documentation, and for pass-
       words, also see in the documentation.

EXAMPLES
   STARTING THE SERVER
       To start up a server:

       $ pg_ctl start

       An example of starting the server, blocking until the server has come up is:

       $ pg_ctl -w start

       For a server using port 5433, and running without fsync, use:

       $ pg_ctl -o "-F -p 5433" start

   STOPPING THE SERVER
       $ pg_ctl stop

       stops the server. Using the -m switch allows one to control how the backend shuts down.

   RESTARTING THE SERVER
       Restarting the server is almost equivalent to stopping the server and starting it again except that pg_ctl saves  and  reuses  the  command
       line options that were passed to the previously running instance. To restart the server in the simplest form, use:

       $ pg_ctl restart

       To restart server, waiting for it to shut down and to come up:

       $ pg_ctl -w restart

       To restart using port 5433 and disabling fsync after restarting:

       $ pg_ctl -o "-F -p 5433" restart

   SHOWING THE SERVER STATUS
       Here is a sample status output from pg_ctl:

       $ pg_ctl status
       pg_ctl: server is running (pid: 13718)
       Command line was:
       /usr/local/pgsql/bin/postgres '-D' '/usr/local/pgsql/data' '-p' '5433' '-B' '128'

       This is the command line that would be invoked in restart mode.

SEE ALSO
       postgres(1)

Application							    2010-05-14								 PG_CTL(1)
All times are GMT -4. The time now is 02:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy