From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: odd behavior in materialized view |
Date: | 2013-03-05 14:06:01 |
Message-ID: | 1362492361.40718.YahooMailNeo@web162904.mail.bf1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> And I found another problem. When I ran the following SQLs in the
> master, PANIC error occurred in the standby.
>
> CREATE TABLE hoge (i int);
> INSERT INTO hoge VALUES (generate_series(1,100));
> CREATE MATERIALIZED VIEW hogeview AS SELECT * FROM hoge;
> VACUUM ANALYZE;
>
> The PANIC error messages that I got in the standby are
>
> WARNING: page 0 of relation base/12297/16387 is uninitialized
> CONTEXT: xlog redo visible: rel 1663/12297/16387; blk 0
> PANIC: WAL contains references to invalid pages
> CONTEXT: xlog redo visible: rel 1663/12297/16387; blk 0
>
> base/12297/16387 is the file of the materialized view 'hogeview'.
Yeah, that looks like it will be fixed by the fix for the first
problem. The write of a first page without any rows to indicate
that it is a scannable empty relation must be WAL-logged. I should
have something later today.
Thanks for spotting this.
--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2013-03-05 14:07:13 | Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |
Previous Message | Robert Haas | 2013-03-05 14:02:05 | Re: Suggested new CF status: "Pending Discussion" |