Re: SPAR Simple PostgreSQL AddOn Replication System

From: "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com>
To: "org(at)kewlstuff(dot)co(dot)za" <org(at)kewlstuff(dot)co(dot)za>
Cc: "PGSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SPAR Simple PostgreSQL AddOn Replication System
Date: 2007-01-12 19:03:52
Message-ID: 65937bea0701121103t5f17727etfda64235314afc7d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/12/07, org(at)kewlstuff(dot)co(dot)za <org(at)kewlstuff(dot)co(dot)za> wrote:
>
>
> Hi Gurjeet.... glad you copied me, else would have missed it.... no longer
> subscribed.
>

I also almost missed your mail. I was monitoring just the conversation
(gmail) that I sent you mail in, but since you changed the subject, it
almost was lost in the other traffic!!!

Maybe you want to post the this reply to the group. I'm now messing around
> with search engines... moved on.
>

CC'ing the list

Looks like you almost got it right, just missing one step.
>
> 1) You use CONFIGURATION to set up the dB connections and yes if they
> green... good.
> then you clicked on ADD SCRIPTS and yes, this puts all the *** supporting
> *** scripts on ALL the dB's for you.
>
> ALSO just make sure the MONITOR (M) selection is checked.... leave all the
> others UNCHECKED.
>
> BUT... SPAR *** doesnt *** assume you want to replicate all your tables...
> so
> Have a look at the TABLE SETUP on the the configuration screen.
>

You mean the the link (Table Setup) on the homepage? Yeah, I did not notice
it, and expected it to work automatically!!!

2) Setup the tables you want to replicate.
> When you click this is will show you all the tables in your dB.... if they
> RED... they cant be replicatied... structure or data wrong... BUT if they
> GREEN then click the INSTALL BOTH option and submit..... that table will
> start replicating.
> What this actually does is activate the trigger on the that table across
> ALL db's for you.
>

For the tables created by the script I sent you earlier, (one int
primary-key, one normal int, columns), the entries are red; I did try the
databases individually, still didn't turn green. One thing though, when I
selected the databases individually, the background turned white, which,
according to comments on that page, means the rep-server was not able to
determine the status of this table.

I stopped the replication server from the control-panel and then fired the
following to create no-primary-key (identical) tables:

psql.exe -p 6543 test -c "create table test1( a int )"
psql.exe -p 5432 test -c "create table test1( a int )"
psql.exe -p 4321 test -c "create table test1( a int )"

And then again went to the 'Table Setup' page and now the new table (test1)
does show-up there, but it is also painted red!!!

Can you tell what is the problem here? Or can you give us a setup, tables
and some data, which can prove that it actually works!

3) START server.... you got that one.
>
> You'll see, the dB is still lightning fast.
> Then just for fun take one server down for a while... make changes to the
> others.... then bring it back... and see what happens.
>
> Thanks for trying Spar... and email me anytime... remember I'm not
> subscribed anymore.
>
> Regards Johnny
>

One more thing Johnny, I asked for sources, others (Jonah) are also asking
for the same. I am sure the community won't show any interest in it if they
don't have the sources. So please consider sending the sources too; and as I
mentioned earlier, you can stick some liberal (preferably BSD) license in
the sources.

Best regards,

--
gurjeet[(dot)singh](at)EnterpriseDB(dot)com
singh(dot)gurjeet(at){ gmail | hotmail | yahoo }.com

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-01-12 19:12:48 Re: [PATCHES] Patch to log usage of temporary
Previous Message Tom Lane 2007-01-12 18:40:31 Idea for fixing the Windows fsync problem