Hi,
We are evaluating BDR for a multi-master cross-datacenter replication, with 2
masters actually communicating across datacenter, supplemented by a local
in-datacenter replicas to provide HA.
Basically, something like
M <——> M
||
S S
I could run all nodes as
> On 08 Oct 2015, at 19:54, Alvaro Herrera wrote:
>
> Oleksii Kliukin wrote:
>
>> Thank you, now it’s clear. I have to say there is no guarantee that
>> the computation would be useless. Someone might be calling a function
>> that updates/deletes rows in the SELE
> On 08 Oct 2015, at 16:00, Adrian Klaver wrote:
>
> On 10/08/2015 01:57 AM, Oleksii Kliukin wrote:
>>
>>> On 06 Oct 2015, at 23:31, Tom Lane >> <mailto:t...@sss.pgh.pa.us>
>>> <mailto:t...@sss.pgh.pa.us <mailto:t...@sss.pgh.pa.us>>&g
> On 06 Oct 2015, at 23:31, Tom Lane wrote:
>
> Oleksii Kliukin writes:
>> This should work, but I'm interested in finding out why the original
>> statement behaves the way Ive described.
>
> plpgsql's SELECT INTO is only capable of storing a single
> On 06 Oct 2015, at 23:11, Adrian Klaver wrote:
>
> On 10/06/2015 02:00 PM, Oleksii Kliukin wrote:
>>
>>> On 06 Oct 2015, at 22:50, Adrian Klaver >> <mailto:adrian.kla...@aklaver.com>> wrote:
>>>
>>> On 10/06/2015 01:48 PM, Oleksii Kl
> On 06 Oct 2015, at 22:50, Adrian Klaver wrote:
>
> On 10/06/2015 01:48 PM, Oleksii Kliukin wrote:
>>
>>> On 06 Oct 2015, at 22:40, Adrian Klaver >> <mailto:adrian.kla...@aklaver.com>
>>> <mailto:adrian.kla...@aklaver.com <mailto:adrian.kla..
> On 06 Oct 2015, at 22:40, Adrian Klaver wrote:
>
> On 10/06/2015 01:13 PM, Oleksii Kliukin wrote:
>>
>> Basically, if we invoke the first example, the foo table with have only
>> 1 row and not 10, as supplied by the generate_series.
>> However, when ORDE
Hello,
I have an issue with a function that is called as a part of the SELECT
INTO target list in pl/pgSQL. I'd like to illustrate it with a simple
example:
DO $$
DECLARE l_id integer;
BEGIN
SELECT test(id) INTO l_id
FROM generate_series(1,10) t(id);
END;
$$ LANGUAGE plpgs
On Tue, Jul 28, 2015 at 10:35 PM, AI Rumman wrote:
> But what I read, in-place upgrade has smaller outage, compared to
> dump/restore.
Please, keep in mind that while the direct outage (when the database
is shut down) is small, there will be a time period right after the
upgrade when PostgreSQL w
