Fujii Masao wrote:
> Ping? ISTM this problem has not been fixed in HEAD yet.
It's next on my list. The other reports seemed more serious and
more likely to be contentious in terms of the best fix.
--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
-
On Fri, Mar 8, 2013 at 1:52 AM, Kevin Grittner wrote:
> Fujii Masao wrote:
>
>> Thanks! I confirmed that the problem that I reported has
>> disappeared in HEAD.
>>
>> Unfortunately I found another odd behavior. When I accessed the
>> MV after VACUUM ANALYZE, I got the following error.
>>
>> E
On Fri, Mar 8, 2013 at 2:42 AM, Kevin Grittner wrote:
> Fujii Masao wrote:
>
>> I found one typo in the document of MV. Please see the attached
>> patch.
>
> Pushed. Thanks!
Thanks!
I found that pg_dump always fails against 9.2 or before server because
of the MV patch.
$ pg_dump
pg_dump: [arc
Fujii Masao wrote:
> I found one typo in the document of MV. Please see the attached
> patch.
Pushed. Thanks!
--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes t
On Fri, Mar 8, 2013 at 1:52 AM, Kevin Grittner wrote:
> Fujii Masao wrote:
>
>> Thanks! I confirmed that the problem that I reported has
>> disappeared in HEAD.
>>
>> Unfortunately I found another odd behavior. When I accessed the
>> MV after VACUUM ANALYZE, I got the following error.
>>
>> E
Fujii Masao wrote:
> Thanks! I confirmed that the problem that I reported has
> disappeared in HEAD.
>
> Unfortunately I found another odd behavior. When I accessed the
> MV after VACUUM ANALYZE, I got the following error.
>
> ERROR: materialized view "hogeview" has not been populated
>
On Thu, Mar 7, 2013 at 8:21 AM, Kevin Grittner wrote:
> Fujii Masao wrote:
>> On Tue, Mar 5, 2013 at 7:36 AM, Kevin Grittner wrote:
>>> Fujii Masao wrote:
>>>
When I accessed the materialized view in the standby server,
>>>
I got the following ERROR message. Looks odd to me. Is this a
Fujii Masao wrote:
> On Tue, Mar 5, 2013 at 7:36 AM, Kevin Grittner wrote:
>> Fujii Masao wrote:
>>
>>> When I accessed the materialized view in the standby server,
>>
>>> I got the following ERROR message. Looks odd to me. Is this a bug?
>>>
>>> ERROR: materialized view "hogeview" has not
Fujii Masao 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;
> VAC
On Tue, Mar 5, 2013 at 7:36 AM, Kevin Grittner wrote:
> Fujii Masao wrote:
>
>> When I accessed the materialized view in the standby server,
>
>> I got the following ERROR message. Looks odd to me. Is this a bug?
>>
>>ERROR: materialized view "hogeview" has not been populated
>>HINT: Us
Fujii Masao wrote:
> When I accessed the materialized view in the standby server,
> I got the following ERROR message. Looks odd to me. Is this a bug?
>
> ERROR: materialized view "hogeview" has not been populated
> HINT: Use the REFRESH MATERIALIZED VIEW command.
>
> The procedure to re
Hi,
When I accessed the materialized view in the standby server,
I got the following ERROR message. Looks odd to me. Is this a bug?
ERROR: materialized view "hogeview" has not been populated
HINT: Use the REFRESH MATERIALIZED VIEW command.
The procedure to reproduce this error message
12 matches
Mail list logo
