Hi,
On 2015-01-13 02:43:26 -0700, deans wrote:
> Hi Craig, any insight on this issue? :)
You've, afaics, not posted your configuration. Could you do so?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training &
Miles Jordan wrote:
> Hi,
>
> I have tables a and b each with around 12 million rows. I am running
> an update query to set the id of table b as an attribute of table a,
> and have an appropriate index on table b that EXPLAIN tells me should
> be used.
>
> The query takes 6 hours on an AWS db.r
Hi,
I have tables a and b each with around 12 million rows. I am running an update
query to set the id of table b as an attribute of table a, and have an
appropriate index on table b that EXPLAIN tells me should be used.
The query takes 6 hours on an AWS db.r3.4xlarge. That seemed hugely excess
:( not yet, still having the issue.
--
View this message in context:
http://postgresql.nabble.com/BDR-Error-restarted-tp5833139p5834821.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make ch
Robert DiFalco wrote:
> Andreas, I think UNLOGGED would be something different but I'm not totally
> clear. However, it seems to me that an unlogged table would simply disappear
> (be truncated) after a server crash. That means instead of maybe loosing a
> record or two that I could loose a ton o
Hi Dean
Did you manage do get any help. I am having the exact issue at the moment.
--
View this message in context:
http://postgresql.nabble.com/BDR-Error-restarted-tp5833139p5834722.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mail
