Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

pgAdmin Query tool Options

-
Use the options that are located under the Query tool node of the tree control to personalize the behavior of the Query tool.
_images/options-query_editor.png
Use the fields on the Query editor dialog to specify workspace preferences for the Query editor:
  • Font - Use the Font selector to specify the font used in the Query tool interface.
  • Max characters per column - Use the Max characters per column field to specify the maximum length of data displayed in a single column.
  • Indent characters - Use the Indent characters field to specify the number of characters to indent with in SQL text boxes.
  • Use spaces instead of tabs - Check the box next to Use spaces instead of tabs to instruct pgAdmin to insert a space when you press the tab key in an SQL text box.
  • Copy SQL from main window to SQL dialogue - Check the box next to Copy SQL from main window to SQL dialogue to instruct pgAdmin to copy any object definition displayed on the main object browser for use as a default query in the Query Tool when the Query Tool opens.
  • Enable Auto ROLLBACK - Check the box next to Enable Auto ROLLBACK to instruct the query tool to execute a ROLLBACK if a query fails.
  • Enable Auto COMMIT - Check the box next to Enable Auto COMMIT to instruct the query tool to enable auto commit after executing the query.
  • Keywords in uppercase - Check the box next to Keywords in uppercase to instruct the Query tool to convert any keywords entered to an uppercase font.
  • External formatting utility - Use the External formatting utility field to provide the name of a formatting tool that can be used to make queries more readable. Use of a tool that provides support for UTF-8 multi-byte characters is not required, but is preferable. The utility must:
    • Accept a STDIN stream and write the result set to STDOUT
    • Provide a result in less than 3 seconds
    • Exit with a code 0 on success
    To use an external formatting tool in the Query Editor:
    • Provide the name of the formatting tool in the External formatting utility field of the Options dialogue.
    • In the Query Editor, select a block of text for formatting, and Press Ctrl+Shift+f, or navigate through the Edit menu to the Format menu, and select External Format.
_images/options-colours.png
Use the fields displayed on the Colours dialog to select colours for items displayed in the Query tool:
  • Foreground/Background - Use the color selectors in the Foreground/Background box to specify background and foreground colors for the Query tool.
  • Caret - Use the color selector in the Caret box to specify a color for the caret (or cursor).
  • SQL Syntax Highlighting - Use the color selectors in the SQL Syntax Highlighting box to specify display colors for syntax components.
_images/options-results_grid.png
Use the fields on the Results Grid dialog to specify display preferences for the results grid.
  • Result copy quoting - Use the Result copy quoting drop-down listbox to specify how fields in a result set should be quoted when copied to the clipboard from the result list. Please Note Disabling this option may prevent copying and pasting rows in the edit grid from functioning properly if the result set contains special characters like line breaks. Specify:
    • None to omit quotes when copied.
    • Strings to quote string values when copied (numeric columns will not be quoted).
    • All to quote all copied values (regardless of data type).
  • Result copy quote character - Use the Result copy quote character drop-down listbox to select a character that will be used to quote the values when copied to the clipboard from the result list. It has no effect if Result copy quoting is set to None.
  • Result copy field separator - Use the Result copy field separator drop-down listbox to select a character that will be used to separate the fields copied to the clipboard from the result list.
  • Show NULL values as <NULL> - Check the box next to Show NULL values as <NULL> to cause NULL values to be shown as <NULL> in the Query Tool’s results grid. Note that this option does not affect data that is exported from the grid, only what is displayed.
  • Thousands separator - Use the Thousands separator field to specify a delimiter character that will be used to break a value into groups of three digits, counting left from the decimal mark.
  • Decimal mark - Use the Decimal mark field to specify a delimiter character that will be used to break a number into an integer portion and a fractional portion.
  • Copy column names - Check the box next to Copy column names to specify that when copying from the result grid, the column name should be included as the first row.
_images/options-query_file.png
Use the fields on the Query File dialog to specify UTF-8 details, and file saving preferences:
  • Read and write Unicode UTF-8 files - Check the box next to Read and write Unicode UTF-8 files to write Unicode UTF-8 files by default.
  • Write BOM for UTF files - Check the box next to Write BOM for UTF files to instruct the query tool to write a byte order mark at the beginning of each file written.
  • Do not prompt for unsaved files on exit - Check the box next to Do not prompt for unsaved files on exit to prevent pgAdmin from prompting you to save SQL queries upon exit.
_images/options-favourites.png
Use the fields on the Favourites dialog to specify a location for the Query tool’s Favourites file:
  • Favourites file path - The Favourites file path field specifies the path to the Query tool’s Favourites file. The default file name is pgadmin_favourites.xml; you can use the Browse button to open a file browser and modify the location of the file.
_images/options-macros.png
Use the fields on the Macros dialog to specify a location for the Query tool’s Macros file:
  • Macros file path - The Macros file path field specifies the path to the Query tool’s Macros file. The default file name is pgadmin_macros.xml; you can use the Browse button to open a file browser and modify the location of the file.
_images/options-history_file.png
Use the fields on the History File dialog to specify user preferences for the Query tool’s history file:
  • History file path - The History file path specifies the path to the Query tool’s history file. The default file name is pgadmin_histoqueries.xml; you can use the Browse button to open a file browser and modify the location of the file.
  • Maximum queries to store in history - Use the Maximum queries to store in history field to specify the number of queries stored by pgAdmin. When the maximum number of queries is reached, the oldest query will be deleted, and a new query will be stored.
  • Maximum size of a stored query (in bytes) - Use the Maximum size of a stored query (in bytes) field to specify the size (in bytes) of the largest query that will be stored in the history file; any query that exceeds the specified size will not be saved in the history file.

Comments

Post a Comment

Popular posts from this blog

How to find the server is whether standby (slave) or primary(master) in Postgresql replication ?

-
Method 1 You can check the mode of the server using "pg_controldata". [pgsql@test~]$ pg_controldata /usr/local/pgsql/data84/ Database cluster state: in archive recovery --> This is Standby Database Database cluster state: in production --> This is Production Database [Master] Method 2 You can use pg_is_in_recovery() which returns True if recovery is still in progress(so the server is running in standby mode or slave) postgres=# select pg_is_in_recovery(); pg_is_in_recovery ------------------- t (1 row) If Return    false   so the server is running in primary mode or master postgres=# select pg_is_in_recovery(); pg_is_in_recovery ------------------- f (1 row)
Read more

7 Steps to configure BDR replication in postgresql

-
Image
 The  BDR  (Bi-Directional Replication) project adds multi-master replication to PostgreSQL 9.4.  Postgres-BDR has a lower impact on the masters(s) than trigger-based replication solutions. There is no write-amplification, as it does not require triggers to write to queue tables in order to replicate writes.   Here We are using  postgres version 9.4.12 and bdr version 1.0.2. for configuring  multi master replication . Simply Following 7 steps you can configure the multi master replication in postgresql. To download the bdr in below link. .   https://github.com/2ndQuadrant/bdr/archive/bdr-pg/REL9_4_12-1.tar.gz $ tar -xzvf REL9_4_12-1.tar.gz $ wget https://github.com/2ndQuadrant/bdr/archive/bdr-plugin/1.0.2.tar.gz $ tar -xzvf 1.0.2.tar.gz 1. To install BDR. $ cd ~/bdr-bdr-pg-REL9_4_12-1 $ ./configure --prefix=/usr/lib/postgresql/9.4 --enable-debug --with-openssl $ make -j4 -s install-world $ cd ~/bdr-bdr-plugin-1.0.2 $ PATH=/usr/lib/postgresql/9.4/bin:"$PATH" ./c
Read more

How to Get Table Size, Database Size, Indexes Size, schema Size, Tablespace Size, column Size in PostgreSQL Database

-
In this post, I am sharing few important function for finding the size of database, table and index in PostgreSQL. Finding object size in postgresql database is very important and common. Is it very useful to know the exact size occupied by the object at the tablespace. The object size in the following scripts is in GB. The scripts have been formatted to work very easily with PUTTY SQL Editor. 1. Checking table size excluding table dependency: SELECT pg_size_pretty(pg_relation_size('mhrordhu_shk.mut_kharedi_audit')); pg_size_pretty ---------------- 238 MB (1 row) 2. Checking table size including table dependency: SELECT pg_size_pretty(pg_total_relation_size('mhrordhu_shk.mut_kharedi_audit')); pg_size_pretty ---------------- 268 MB (1 row) 3. Finding individual postgresql database size SELECT pg_size_pretty(pg_database_size('db_name')); 4. Finding individual table size for postgresql database -including dependency index: SELECT pg_size_pretty(pg_total_rel
Read more

Ora2PG - Oracle/MySQL to Postgres DB migration Version 20.0

-
Ora2Pg is a free tool used to  migrate  an  Oracle  or MySQL database to a  PostgreSQL  compatible schema. It connects your  Oracle  database, scan it automatically and extracts its structure or data, it then generates SQL scripts that you can load into your  PostgreSQL  database. ora2pg version 20.0 software : ora2pg-20.0.tar ora2pg-20.0   https://github.com/darold/ora2pg/releases/tag/v20.0 Some Blogs about DB Migration : https://2ndquadrant.in/postgresmigration/oracle-to-postgresql-migration/ https://2ndquadrant.in/database-migration-from-oracle-to-postgres/ INSTALLATION All Perl modules can always be found at CPAN ( http://search.cpan.org/ ). Just type the full name of the module (ex: DBD::Oracle) into the search input box, it will brings you the page for download. Releases of Ora2Pg stay at SF.net ( https://sourceforge.net/projects/ora2pg/ ). Under Windows you should install Strawberry Perl ( http://strawberryperl.com/ ) and the OSes corresponding Oracle clients. I
Read more

PostgreSQL Introduction

-
PostgreSQL tutorial provides basic and advanced concepts of SQL. Our PostgreSQL tutorial is designed for beginners and professionals. PostgreSQL is an opens-source object-relational database management system (ORDBMS). Our PostgreSQL tutorial includes all topics of PostgreSQL language such as create database, create table, drop database, drop table, select database, select table, insert record, update record, delete record, triggers, functions, procedures, cursors etc. There are also given PostgreSQL interview questions and quizzes to help you better understand the PostgreSQL language. Prerequisite: Before you start doing practice with various types of examples given in this reference, I'm making an assumption that you are already aware about what is database, especially RDBMS and what is a computer programming language. you must have the basic knowledge of SQL Problem: We assure that you will not find any problem in this PostgreSQL tutorial. But if there is any mistake
Read more