Steve Holdoway | 2 Mar 07:31 2009
Picon

Slony 2.0.1 installation problems...

Hey folks, 

Unfortunately there's a few too many unknowns in this one, but if anyone can help I'd be really grateful.

I have a debian 64bit/postgres 8.3.6/slony 2.0.0 system up and running, and have been happily developing
on this

I Installed from ubuntu hardy,

ii  postgresql-8.3              8.3.6-0ubuntu8.04                           
ii  postgresql-client-8.3       8.3.6-0ubuntu8.04                           
ii  postgresql-client-common    87                                          
ii  postgresql-common           87                                          
ii  postgresql-contrib-8.3      8.3.6-0ubuntu8.04                           
ii  postgresql-doc-8.3          8.3.6-0ubuntu8.04                           
ii  postgresql-server-dev-8.3   8.3.6-0ubuntu8.04                  

And built slony 2.0.0 from source. All works fine.

However, on another server, running 64bit Centos 5.2/postgres 8.3.6/slony 2.0.1, I can't get the slonik
store node to run. It fails with 

 PGRES_FATAL_ERROR load '$libdir/slony1_funcs';  - ERROR:  could not access file
"$libdir/slony1_funcs": No such file or directory

I've installed the following from the pgdg yum repository:
postgresql-libs-8.3.6-1PGDG.rhel5
postgresql-pltcl-8.3.6-1PGDG.rhel5
postgresql-devel-8.3.6-1PGDG.rhel5
postgresql-8.3.6-1PGDG.rhel5
(Continue reading)

Can't checkout Slony1-www repository

hi !

One year ago, i announced on this list that some french slony users were
gathering to translate the official documentation :

http://listes.postgresql.fr/pipermail/slony-traduction/2008-February/000006.html

The good news is that we're almost done !  In a few days, we will put
online slony's french documentation for both 1.2 and 2.0 branches. The
doc will be available on  postgresql.fr website.

We also want to create slony.fr website, and as we're a bit lazy, we
only want to translate the slony.info website.

Here comes trouble : when we try to fetch the website files, we are
rejected :

$ export CVSROOT=":pserver:anonymous@...:/slony1"
$ cvs co slony1-www/
cvs checkout: Updating slony1-www
cvs checkout: failed to create lock directory for `/slony1/slony1-www'
(/slony1/slony1-www/#cvs.lock): Permission denied
cvs checkout: failed to obtain dir lock in repository `/slony1/slony1-www'
cvs [checkout aborted]: read lock failed - giving up

It seems the server doesn't like anonymous login for the slony1-www
repository :-/

Are we doing something the wrong way ? Is there another method to access
these files ?
(Continue reading)

Christopher Browne | 2 Mar 17:13 2009

Re: how to sync laptop master to server slave?

Niels Olson <niels.olson@...> writes:
> I'm a medical student running a wiki on my laptop for notes, it's
> critical to have access offline.
>
> book + computer = good
> book + internet = bad
>
> Offline access is more important than online access. But it would be
> awfully nice to have online access when I can't get to my laptop. I
> have identical versions of Postgres (8.3.6) and wiki software. Would
> Slony be able to help with that? Are there any problems with the
> laptop being a laptop, frequently on small local networks without
> valid NAT?
>
> Should I run it the server as master and the laptop as slave?

Unfortunately, I don't think this is likely to be a very good "use
case" for Slony-I.

As per the documentation...

   "Slony-I is a system intended for data centers and backup sites,
   where the normal mode of operation is that all nodes are available
   all the time, and where all nodes can be secured. If you have nodes
   that are likely to regularly drop onto and off of the network, or
   have nodes that cannot be kept secure, Slony-I is probably not the
   ideal replication solution for you."

The trouble with your scenario is that, with sporadic and changing
connectivity, there would be two notable "emergent problems":
(Continue reading)

Steve Holdoway | 2 Mar 22:06 2009
Picon

Re: Slony 2.0.1 installation problems...

Sorry, complete brain fade. Once I'd installed slony on the client node, all ran fine.

Never could get the hang of Mondays!

Steve
On Mon, 2 Mar 2009 19:31:09 +1300
Steve Holdoway <steve@...> wrote:

> Hey folks, 
> 
> Unfortunately there's a few too many unknowns in this one, but if anyone can help I'd be really grateful.
> 
> I have a debian 64bit/postgres 8.3.6/slony 2.0.0 system up and running, and have been happily developing
on this
> 
> I Installed from ubuntu hardy,
>  
> ii  postgresql-8.3              8.3.6-0ubuntu8.04                           
> ii  postgresql-client-8.3       8.3.6-0ubuntu8.04                           
> ii  postgresql-client-common    87                                          
> ii  postgresql-common           87                                          
> ii  postgresql-contrib-8.3      8.3.6-0ubuntu8.04                           
> ii  postgresql-doc-8.3          8.3.6-0ubuntu8.04                           
> ii  postgresql-server-dev-8.3   8.3.6-0ubuntu8.04                  
> 
> And built slony 2.0.0 from source. All works fine.
> 
> However, on another server, running 64bit Centos 5.2/postgres 8.3.6/slony 2.0.1, I can't get the slonik
store node to run. It fails with 
> 
(Continue reading)

Vick Khera | 2 Mar 22:31 2009

Re: how to sync laptop master to server slave?

On Fri, Feb 27, 2009 at 11:43 PM, Niels Olson <niels.olson@...> wrote:
> I'm a medical student running a wiki on my laptop for notes, it's
> critical to have access offline.
>
> book + computer = good
> book + internet = bad
>

Check out alternate wiki software... for personal notes, I really like
TiddlyWiki as it is 100% self-contained in a single HTML + JavaScript
file.  Just copy it back and forth with your "online" version.  I
assume you don't edit it in multiple places without possibility of
syncing your changes before you move.
Geoffrey | 4 Mar 13:49 2009

Re: adding a field to a replicated table

Christopher Browne wrote:
> Geoffrey <lists@...> writes:
>> As I've noted in the past, because of our software design, I can not
>> use the 'execute script' process for adding a field to a table.  That
>> being said, I'm looking for an alternative approach.  As it stands,
>> when we need to add a table, we plan to shut slony down, create a new
>> set for that table and restart slony.
>>
>> What would be the best way to add a field to a replicated table using
>> this scenario?  That is, shutting slony down, making the change and
>> starting slony back up.  I'm assuming that I can't simply add the
>> field to both nodes and restart slony, but if that would work, that
>> would be great.
.
.
<snip>
.
.
> The amount of "surgery" you seem to want to do concerns me somewhat...
> It sounds likely to lead to an unhappy ending, and unhappy users
> aren't what we want.

After reviewing your concerns, I've come up with a different approach to 
this problem, which really is probably a whole lot better then my 
previous idea.  That being said, I'm still going to have to set the 
slony triggers to 'fire always' but I'd like some input on my solution.

The idea is that since I'm going to likely have to lock my users out of 
the database when I add a field to a table, why not simply use the 
'execute script' solution anyway.  That is:
(Continue reading)

Geoffrey | 4 Mar 21:53 2009

execute script error

I'm trying to run, what I would think would be a very simple 'execute 
script' but I'm getting:

<stdin>:1: ERROR: syntax error at or near execute

Here is the relevant section of code:

SETID=2
SCRIPT=people.sql

/usr/bin/slonik <<EOF
execute script ( SET ID = $SETID, FILENAME = '$SCRIPT', EVENT NODE = 1);
EOF

What am I missing???

--

-- 
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
  - Benjamin Franklin
Jan Wieck | 4 Mar 21:04 2009
Picon

Re: execute script error

On 3/4/2009 3:53 PM, Geoffrey wrote:
> I'm trying to run, what I would think would be a very simple 'execute 
> script' but I'm getting:
> 
> <stdin>:1: ERROR: syntax error at or near execute
> 
> Here is the relevant section of code:
> 
> 
> SETID=2
> SCRIPT=people.sql
> 
> 
> /usr/bin/slonik <<EOF
> execute script ( SET ID = $SETID, FILENAME = '$SCRIPT', EVENT NODE = 1);
> EOF
> 
> What am I missing???
> 

The admin conninfo statements at the beginning of the script.

Jan

--

-- 
Anyone who trades liberty for security deserves neither
liberty nor security. -- Benjamin Franklin
Geoffrey | 4 Mar 22:02 2009

Re: execute script error

Geoffrey wrote:
> I'm trying to run, what I would think would be a very simple 'execute 
> script' but I'm getting:
> 
> <stdin>:1: ERROR: syntax error at or near execute
> 
> Here is the relevant section of code:
> 
> 
> SETID=2
> SCRIPT=people.sql
> 
> 
> /usr/bin/slonik <<EOF
> execute script ( SET ID = $SETID, FILENAME = '$SCRIPT', EVENT NODE = 1);
> EOF
> 
> What am I missing???

No sooner then I send the message, google got friendly.  Seems I was 
missing the conn info and the cluster name.

--

-- 
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
  - Benjamin Franklin
Geoffrey Myers | 4 Mar 22:05 2009

execute script question

As I understand it, 'execute script' will cause the slony triggers to be 
deleted and then re-added.  If my 'execute script' only touches one 
table, are all the slony triggers on all tables deleted and re-added, or 
is it only those tables affected by the 'execute script?'

--

-- 
Geoffrey Myers
Myers Consulting Inc.
770.592.1651

Gmane