| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | vitus(at)wagner(dot)pp(dot)ru |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Proposal: Implement failover on libpq connect level. |
| Date: | 2015-08-19 03:42:45 |
| Message-ID: | 20150819.124245.1322750734243127189.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
I wonder how extended protocol is handled by this proposal. Suppose
load balacing mode is enabled. PQprepare is executed on standby1. Then
PQexecPrepared gets called. This may be executed on standby2, which
will fail because there's no prepared statement created by the former
PQprepare call.
Even simple procotol is used, same thing can be said to SQL
PREPARE/EXECUTE/DEALLOCATE.
SQL BEGIN/COMMIT/ROLLBACK would be more interesting example in load
balancing mode.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kouhei Kaigai | 2015-08-19 04:19:38 | Re: Bug? ExecChooseHashTableSize() got assertion failed with crazy number of rows |
| Previous Message | Amit Kapila | 2015-08-19 03:27:11 | Re: [DESIGN] ParallelAppend |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 'Victor Wagner *EXTERN*' | 2015-08-19 06:51:47 | Re: Proposal: Implement failover on libpq connect level. |
| Previous Message | Amit Kapila | 2015-08-19 02:58:32 | Re: Proposal: Implement failover on libpq connect level. |