> On Thursday, 13 June 2019, 18:11:34 BST, Christopher Browne
wrote: On Thu, 13 Jun 2019 at 12:48, Tory M Blue
wrote:
I saw nothing in the locks when I looked. We did notice that in our second
dump, while we are using a -n table, we are not including a -N _slonschema,.
Now that should
On Thu, 13 Jun 2019 at 12:48, Tory M Blue wrote:
> I saw nothing in the locks when I looked. We did notice that in our second
> dump, while we are using a -n table, we are not including a -N
> _slonschema,. Now that should work!! but we are going to add the -N
> _slonschema as well as the -n
On Thu, Jun 13, 2019 at 7:59 AM Christopher Browne
wrote:
> On Wed, Jun 12, 2019 at 11:58 PM Tory M Blue wrote:
>
>> First postgres 9.x
>> CentOS 7.2
>> Replication flows:
>> primary ->secondary-> 3 query slaves
>>
>> Okay here it is,
>>
>> My dump started:
>>
>> Start export of schema clsdb
On Wed, Jun 12, 2019 at 9:33 AM Christopher Browne
wrote:
> On Tue, Jun 11, 2019 at 3:44 PM Tory M Blue wrote:
>
>>
>>
>> On Tue, Jun 11, 2019 at 12:26 PM Christopher Browne <
>> cbbro...@afilias.info> wrote:
>>
>>>
>>>
>>> On Tue, Jun 11, 2019 at 1:30 PM Tory M Blue wrote:
>>>
I'm
On Tue, Jun 11, 2019 at 3:44 PM Tory M Blue wrote:
>
>
> On Tue, Jun 11, 2019 at 12:26 PM Christopher Browne
> wrote:
>
>>
>>
>> On Tue, Jun 11, 2019 at 1:30 PM Tory M Blue wrote:
>>
>>> I'm wondering if there is anything I can do to prevent what appears to
>>> be slony replication backup (not
On Tue, 11 Jun 2019, Tory M Blue wrote:
Ya will take a look, I also thought that bypassing the slon schema would solve
it but apparently not, we
can have 2-10million count in the sl_log before it clears and it's apparent
that the replication is not
happening, so I'll poke around some more.
On Tue, Jun 11, 2019 at 12:26 PM Christopher Browne
wrote:
>
>
> On Tue, Jun 11, 2019 at 1:30 PM Tory M Blue wrote:
>
>> I'm wondering if there is anything I can do to prevent what appears to be
>> slony replication backup (not replicating) during a pg_dump. I'm using a -N
>> slonschema, so
