Hey Craig thank you very much for your response.
> When you say you "attempted to" - what was the outcome?
I tried a truncate without the cascade option. After that I tried it with
the cascade option. The session just hanged indefinitely at that point.
There was no rollback and I was testing on a
-j4 -s all make -s install
make: *** No rule to make target `make'. Stop.
make: *** Waiting for unfinished jobs
Many thanks,
Will McCormick
I have a script which is meant to remove a node from bdr replication. Two
nodes in replication node A and node B. The script does the following.
1. On node A - SELECT bdr.bdr_part_by_node_names(ARRAY['node B']);
2. On node A -Checks that the node_status is marked as 'k' in bdr.bdr_nodes
3. I th
What viable options exist for Backup & Recovery in a BDR environment? From
the reading I have done PITR recovery is not an option with BDR. It's
important to preface this that I have almost no exposure to postgres backup
and recovery. Is PITR not an option with BDR?
If a user fat fingers something
cannot
perform PITR?
On Wed, Nov 18, 2015 at 11:19 AM, Jim Nasby
wrote:
> On 11/18/15 9:46 AM, Will McCormick wrote:
>
>> What viable options exist for Backup & Recovery in a BDR environment?
>> From the reading I have done PITR recovery is not an option with BDR.
>>
Basic backup and recovery question. I want to perform complete restore and
recovery using continuous archive mode.
Lets imagine we have a single table MYTABLE. Here are my high level steps
1) Add a record A) to MYTABLE
2) Take a file system backup to be used for recovery. This backup includes
ar
I inherited a 9.1 replication environment
Few basic questions that I can't find clear answers / clarifications for if
possible:
3 types of replication in 9.1 I've read about from the offical docs:
1) warm standby
2) hot standby
3) streaming replication
I'm using streaming replication I believe,
Thanks a ton for the prompt response.
I've read most of this but some it was not clear until we discussed.
Updated with WLM:
On 12/17/2015 07:17 AM, Will McCormick wrote:
>
> I inherited a 9.1 replication environment
>
> Few basic questions that I can't find clear answer
Thanks for the great assistance
On Thu, Dec 17, 2015 at 11:27 AM, Adrian Klaver
wrote:
> On 12/17/2015 07:56 AM, Will McCormick wrote:
>
>> Thanks a ton for the prompt response.
>>
>> I've read most of this but some it was not clear until we discussed.
>>
ery.
On Thu, Dec 17, 2015 at 11:27 AM, Adrian Klaver
wrote:
> On 12/17/2015 07:56 AM, Will McCormick wrote:
>
>> Thanks a ton for the prompt response.
>>
>> I've read most of this but some it was not clear until we discussed.
>>
>> Updated with WLM:
>&g
Why does this not work? From what I read only default values should cause
issue. I'm on release 9.4.4:
bms=# ALTER TABLE trap ALTER COLUMN trap_timestamp TYPE TIMESTAMP WITH TIME
ZONE;
ERROR: ALTER TABLE ... ALTER COLUMN TYPE may only affect UNLOGGED or
TEMPORARY
tables when BDR is active; trap
Hi All,
And sorry about that damn thumb pad! Premature send!
On Wed, Apr 27, 2016 at 10:15 AM, Adrian Klaver
wrote:
> On 04/27/2016 07:11 AM, Will McCormick wrote:
>
>> Why does this not work:
>>
>>
> Because it is NULL :)?
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>
Why does this not work:
laver
wrote:
> On 04/27/2016 07:13 AM, Will McCormick wrote:
>
>> Why does this not work? From what I read only default values should
>> cause issue. I'm on release 9.4.4:
>>
>>
>> bms=# ALTER TABLE trap ALTER COLUMN trap_timestamp TYPE TIMESTAMP WITH
I guess the only viable option would be to the check explicitly ourselves.
On Wed, Apr 27, 2016 at 11:25 AM, Will McCormick
wrote:
> But this is the exact column definition that exists on the table when I
> execute the statement
>
> It's like it does not check the pre-exis
So if I wanted to extend a column from 100 characters to 255 characters is
this permitted? The fact that I'm not making a change and the BDR kicked me
out makes me skeptical.
On Wed, Apr 27, 2016 at 11:56 AM, Craig Ringer
wrote:
> On 27 April 2016 at 23:43, Alvaro Aguayo Garcia-Rada <
> aagu...@
A reason to consider may be portability. What happens if I want to let my
customer chose their data store or I just don't want to put all my eggs in
one basket.Technically there are truths but you cannot ignore the business
side either. If a we can exceed our performance requirements and keep
thing
ve to replace a million lines of code if you plan upfront. If you
don't .. you do.
On Wed, May 4, 2016 at 11:29 AM, Uwe Schroeder wrote:
> On Wed, May 04, 2016 11:05:25 AM Will McCormick wrote:
>
> A reason to consider may be portability. What happens if I want to let my
> cust
n
opportunity to really make a difference and get more aligned with your
development staff. Doesn't matter what code base DAO's are in it's a
repetitive pattern that any database person can pick up.
On Wed, May 4, 2016 at 12:29 PM, Szymon Lipiński wrote:
>
>
> On 4 May 2
l (pun not intended) for the job.
On Wed, May 4, 2016 at 1:33 PM, Szymon Lipiński wrote:
>
>
> On 4 May 2016 at 19:09, Will McCormick wrote:
>
>> I agree that it's not like turning on the light switch. And I'm not
>> implying there isn't a logic layer between
Yeah but your already paying for a developer ...
On Wed, May 4, 2016 at 2:36 PM, Szymon Lipiński wrote:
>
>
> On 4 May 2016 at 20:20, Will McCormick wrote:
>
>> I 100% agree with you. It's always been a problem but it is up to us to
>> take ownership and provide va
21 matches
Mail list logo
