On Tue, Apr 23, 2013 at 11:05 PM, Andres Freund and...@2ndquadrant.comwrote:
On 2013-04-23 19:33:24 +0530, Jeevan Chalke wrote:
On Tue, Apr 23, 2013 at 7:01 PM, Merlin Moncure mmonc...@gmail.com
wrote:
On Tue, Apr 23, 2013 at 7:18 AM, Jeevan Chalke
jeevan.cha...@enterprisedb.com
On Wed, Apr 24, 2013 at 3:04 AM, Kevin Grittner kgri...@ymail.com wrote:
Jeevan Chalke jeevan.cha...@enterprisedb.com wrote:
On Mon, Apr 22, 2013 at 6:41 PM, Andres Freund and...@2ndquadrant.com
wrote:
On 2013-04-22 18:35:04 +0530, Jeevan Chalke wrote:
I have observed that following
Jeevan Chalke jeevan.cha...@enterprisedb.com wrote:
On Wed, Apr 24, 2013 at 3:04 AM, Kevin Grittner kgri...@ymail.com wrote:
Any objections to the attached to fix this issue?
Nope. Fine with me.
Pushed. Thanks for the report!
--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The
Hi Tom,
Since we are close to release, we should not have crashes like this.
Please have a look. My patch may not be correct as I haven't looked closely.
Thanks
On Mon, Apr 22, 2013 at 7:28 PM, Jeevan Chalke
jeevan.cha...@enterprisedb.com wrote:
On Mon, Apr 22, 2013 at 6:41 PM, Andres
Hi,
On 2013-04-23 17:48:49 +0530, Jeevan Chalke wrote:
Hi Tom,
Since we are close to release, we should not have crashes like this.
Please have a look. My patch may not be correct as I haven't looked closely.
Isn't that Kevin's departement?
Andres
--
Andres Freund
Andres Freund and...@2ndquadrant.com wrote:
On 2013-04-23 17:48:49 +0530, Jeevan Chalke wrote:
Hi Tom,
Since we are close to release, we should not have crashes like
this.
Please have a look. My patch may not be correct as I haven't
looked closely.
Isn't that Kevin's departement?
I'll
On Tue, Apr 23, 2013 at 7:18 AM, Jeevan Chalke
jeevan.cha...@enterprisedb.com wrote:
Hi Tom,
Since we are close to release, we should not have crashes like this.
huh? we are not even in beta yet
merlin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
On Tue, Apr 23, 2013 at 7:01 PM, Merlin Moncure mmonc...@gmail.com wrote:
On Tue, Apr 23, 2013 at 7:18 AM, Jeevan Chalke
jeevan.cha...@enterprisedb.com wrote:
Hi Tom,
Since we are close to release, we should not have crashes like this.
huh? we are not even in beta yet
I mean, beta
On 2013-04-23 19:33:24 +0530, Jeevan Chalke wrote:
On Tue, Apr 23, 2013 at 7:01 PM, Merlin Moncure mmonc...@gmail.com wrote:
On Tue, Apr 23, 2013 at 7:18 AM, Jeevan Chalke
jeevan.cha...@enterprisedb.com wrote:
Hi Tom,
Since we are close to release, we should not have crashes like
Jeevan Chalke jeevan.cha...@enterprisedb.com wrote:
On Mon, Apr 22, 2013 at 6:41 PM, Andres Freund and...@2ndquadrant.com wrote:
On 2013-04-22 18:35:04 +0530, Jeevan Chalke wrote:
I have observed that following sequence is causing server crash.
CREATE MATERIALIZED VIEW temp_class_mv AS
Hi,
I have observed that following sequence is causing server crash.
CREATE MATERIALIZED VIEW temp_class_mv AS
SELECT * FROM pg_class
WITH NO DATA;
CREATE OR REPLACE FUNCTION test_refresh_mv()
RETURNS int
AS $$
BEGIN
REFRESH MATERIALIZED VIEW temp_class_mv;
return 1;
END; $$ LANGUAGE
On 2013-04-22 18:35:04 +0530, Jeevan Chalke wrote:
Hi,
I have observed that following sequence is causing server crash.
CREATE MATERIALIZED VIEW temp_class_mv AS
SELECT * FROM pg_class
WITH NO DATA;
CREATE OR REPLACE FUNCTION test_refresh_mv()
RETURNS int
AS $$
BEGIN
REFRESH
On Mon, Apr 22, 2013 at 6:41 PM, Andres Freund and...@2ndquadrant.comwrote:
On 2013-04-22 18:35:04 +0530, Jeevan Chalke wrote:
Hi,
I have observed that following sequence is causing server crash.
CREATE MATERIALIZED VIEW temp_class_mv AS
SELECT * FROM pg_class
WITH NO DATA;
13 matches
Mail list logo