| From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
|---|---|
| To: | 乔志强 <qiaozhiqiang(at)leadcoretech(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [streaming replication] 9.1.3 streaming replication bug ? |
| Date: | 2012-04-09 13:49:25 |
| Message-ID: | 4F82E8E5.4090807@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On 04/09/2012 03:33 AM, 乔志强 wrote:
>
> But after some minutes the master output:
> requested WAL segment XXX has already been removed
> the standby output:
> FATAL: could not receive data from WAL stream: FATAL: requested WAL segment XXX
> has already been removed
>
>
> Question:
> Why the master deletes the WAL segment before send to standby in synchronous mode? It is a streaming replication bug ?
>
>
> ////////////////////////////////////////
>
> master server output:
> LOG: database system was interrupted; last known up at 2012-03-30 15:37:03 HKT
> LOG: database system was not properly shut down; automatic recovery in progress
My question would be, what happened above? In other words what does the
log prior to this one show just before the database shutdown?
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | leaf_yxj | 2012-04-09 13:52:36 | Re: Questions of the privileges to use the pg_cancel_backend and pg_terminate_backend function. Thanks. |
| Previous Message | Condor | 2012-04-09 13:32:30 | Re: [streaming replication] 9.1.3 streaming replication bug ? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-04-09 13:50:59 | Re: About the behavior of array_length() for empty array |
| Previous Message | Andres Freund | 2012-04-09 13:35:06 | Deprecating non-select rules (was Re: Last gasp) |