Re: [GENERAL] Installing Postgresql on Linux Friendlyarm

2014-09-25 Thread Xiang Gan
Finally, I managed to run Postgresql in Linux FriendlyARM environment. It seems that Postgresql server starts to work, however, it prints out some WARNING info. during the start. The error info. is as follows: LOG: could not resolve localhost: Temporary failure in name resolution LOG: disabling

Re: [GENERAL] deadlock of lock-waits (on transaction and on tuple) using same update statement

2014-09-25 Thread Andrej Vanek
Hi Bill, thanks for your answer. most often caused by something earlier in the transactions need all of the statements in each transaction It would be great if we could reveal an application error. Whole transactions I've already posted (in postgres log: log_min_duration_statement=0).

Re: [GENERAL] deadlock of lock-waits (on transaction and on tuple) using same update statement

2014-09-25 Thread Andrej Vanek
Hi, now I've checked release-notes of 9.3.5 (my version 9.3.4)- found a fix which probably could lead to my deadlocks: Fix race condition when updating a tuple concurrently locked by another process (Andres Freund,Álvaro Herrera) How can I make sure I've run into this bug?

Re: [GENERAL] How to clone CURRENT_DATE to SYSDATE ?

2014-09-25 Thread Emanuel Araújo
Thank's Adrian, I want really create another CURRENT_DATE called SYSDATE. postgres=# SELECT CURRENT_DATE ; date 2014-09-25 (1 row) I need that: postgres=# SELECT SYSDATE ; date 2014-09-25 Because, I am trying SymmetricDS between Oracle and PostgreSQL, in my

Re: [GENERAL] How to clone CURRENT_DATE to SYSDATE ?

2014-09-25 Thread Pavel Stehule
Hi 2014-09-25 12:24 GMT+02:00 Emanuel Araújo eac...@gmail.com: Thank's Adrian, I want really create another CURRENT_DATE called SYSDATE. It needs a hack to postgres. Pseudoconstant functions needs a support in PostgreSQL parser. There is no other possibility Pavel postgres=# SELECT

Re: [GENERAL] Synchronous replication + pgPool: not all transactions immediately visible on standby

2014-09-25 Thread Michael Paquier
On Thu, Sep 25, 2014 at 8:40 AM, Tatsuo Ishii is...@postgresql.org wrote: Postgres-XC (or Postgres-XL which is a fork of Postgres-XC) overcomes the issue by using global transaction management technique. ... At the cost of reducing data availability for sharded tables, and increasing write load

Re: [GENERAL] How to clone CURRENT_DATE to SYSDATE ?

2014-09-25 Thread Adrian Klaver
On 09/25/2014 03:24 AM, Emanuel Araújo wrote: Thank's Adrian, I want really create another CURRENT_DATE called SYSDATE. postgres=# SELECT CURRENT_DATE ; date 2014-09-25 (1 row) I need that: postgres=# SELECT SYSDATE ; date 2014-09-25 Because, I am

Re: [GENERAL] Installing Postgresql on Linux Friendlyarm

2014-09-25 Thread Adrian Klaver
On 09/24/2014 11:34 PM, Xiang Gan wrote: Finally, I managed to run Postgresql in Linux FriendlyARM environment. It seems that Postgresql server starts to work, however, it prints out some WARNING info. during the start. The error info. is as follows: LOG: could not resolve localhost:

Re: [GENERAL] deadlock of lock-waits (on transaction and on tuple) using same update statement

2014-09-25 Thread Alvaro Herrera
Andrej Vanek wrote: Hi, now I've checked release-notes of 9.3.5 (my version 9.3.4)- found a fix which probably could lead to my deadlocks: Fix race condition when updating a tuple concurrently locked by another process (Andres Freund,Álvaro Herrera) How can I make sure I've run

[GENERAL] Re: Synchronous replication + pgPool: not all transactions immediately visible on standby

2014-09-25 Thread Thomas Kellerer
I think your problem is not relevant to pgpool-II. PostgreSQL's synchronous replication is actually not synchronous (it's confusing but the naming was developer's decision). Primary server sends the committed transaction's WAL record to standby and wait for it is written to the standby's

Re: [GENERAL] Synchronous replication + pgPool: not all transactions immediately visible on standby

2014-09-25 Thread Kevin Grittner
Tatsuo Ishii is...@postgresql.org wrote: I think your problem is not relevant to pgpool-II. Agreed. PostgreSQL's synchronous replication is actually not synchronous Well, that statement is a bit misleading. What is synchronous with the COMMIT request is that data is persisted on at least

Re: [GENERAL] Re: Synchronous replication + pgPool: not all transactions immediately visible on standby

2014-09-25 Thread Tatsuo Ishii
If you dislike the PostgreSQL's behavior, you may want to try pgpool-II's native replication mode (set replication_mode = on and master_slave_mode = off). In the mode, pgpool-II does not return response to the client until all PostgreSQL returns a commit response. Thus right after the commit,

Re: [GENERAL] Synchronous replication + pgPool: not all transactions immediately visible on standby

2014-09-25 Thread Tatsuo Ishii
PostgreSQL's synchronous replication is actually not synchronous Well, that statement is a bit misleading. What is synchronous with the COMMIT request is that data is persisted on at least two targets before the COMMIT request returns an indication of success. It guarantees that much

[GENERAL] Off Topic: Anybody reading this via news.gmane.org?

2014-09-25 Thread George Neuner
Just wondering if anyone else reads this list via gmane and also is having problems? I follow several lists via gmane and a few days ago all my posts started being rejected - no authorization email, just an immediate you are not allowed to post error. Then 2 days ago, I also lost read

Re: [GENERAL] Off Topic: Anybody reading this via news.gmane.org?

2014-09-25 Thread Ian Pilcher
No problem reading (and hopefully posting) via Gmane here. -- Ian Pilcher arequip...@gmail.com I grew up before Mark Zuckerberg invented friendship