About saurabhs

Hi  jsoler,   Please find an explanation for the statement.   If any transaction gets aborted, the transaction clean up won't occur properly, hence it stops the mainline code from completing the functionality. So, the fixed is provided to protect again above explained scenario in cases where it ought to return to the mainline code, but allow it where there's an interruptible process happening. The timeout can cause such scenarios (statement_timeout). Also, this might also be caused by lock_timeout.   Hope this clarifies the raised concerns.  ... View more

Hi  jwoodsford ,   By looking at your reported query, there might be multiple reasons which can slow down the database performance. Also, as per mentioned by "alexc168", I/O could be one of the reasons for slowness.   However, we would recommend the generic area from the troubleshooting point of view.   Monitor the disk I/O as mentioned by "alexc168". Execute the statements in transaction batches. (i.e BEGIN.....COMMIT) Verify there is no blocking issue with parallel UPDATE statements. wal_buffers, checkpoint, bg_writer are tuned enough. If possible replace "INSERT" with "COPY" as it increases the performance.  - Refer the following link for the usage of "COPY" statement. https://www.postgresql.org/docs/10/populate.html 6. Network latency. Hope this helps. ... View more

Hi  sheila1372,   There are no existing statistics table or view which maintains this information on the database.   Following are the ways from which you can achieve this :  Logging : Setting the logging parameters which will collect the details into the database logs :  i.  logging_collector -- This will enable logging ii. log_line_prefix -- What all to log iii. log_statement -- Which statements to log   Note: This change will cause extra logging. Please make sure adequate disk space is available.   Creating Triggers : i. Create an audit table to maintain such records. ii. Create a function which will collect the user name for the respective operation and will insert it into the audit table. iii. Create a trigger on the audit table which will invoke the function created above for DML operations.   Note: Please test the trigger creation method is on test environment prior to applying on production, as it might cause the slowness for complex queries. ... View more

Hi  davejung,   Thank you for reporting the issue with us.    We are working on it and we will udpate you soon. Meanwhile, c ould you please confirm on the pgpool version. ... View more

Hi Tom,   Thank you for your time and patience.     As per documentation under supported platforms, EFM-3.1 is compatible with SLES12. However, the builds are not yet available. The documentation and the release information will be updated once the builds are ready.   Please let us know in case of any issues/queries. ... View more

Hi Akash,   The exception you have received is due to invalid value has been provided for the parameter "SSL Mode". The valid values for the "SSL Mode" parmeter is "Require,Prefer, Disable".    Also, find the below link for the reference: http://www.npgsql.org/doc/connection-string-parameters.html   Can you please try it once with the above options and let us know if you face the issue again. ... View more

Hi   erik ,   There is no such default password for user Postgres. The password needs to be set.    Please find below details:   1.   Login   to the machine where PostgreSQL is installed. Use below command from terminal to connect to the cluster.    psql   -U   postgres    - If the PATH is not set, above command will give an error. Below is the default PATH for PostgreSQL binaries.   /Applications/Postgres.app/Contents/Versions/latest/bin/   2. After successful login use below command to set the password:   ALTER ROLE postgres PASSWORD 'postgres';   Hope this helps. ... View more

Hi  l gwapnitsky,   Using VIP In this case will be wise decision. The VIP remains active on Master and moves on to the Slave in case of failover.   Hope this helps. ... View more