|
Home > Archive > Slony1 PostgreSQL Replication > June 2005 > Slony1 1.1.0 slonik segfault on create set.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Slony1 1.1.0 slonik segfault on create set.
|
|
| Tony Byrne 2005-06-30, 7:25 am |
| Hi guys,
Just a quick note to say that I encountered a small problem after I
upgraded to Slony1 1.1.0. On trying to create a new set slonik would
segfault and coredump. I solved the problem by adding a comment
attribute in my 'create set' command, but surely it's legal not to
specify a comment for a set?
Regards,
Tony.
--
Tony Byrne
| |
| Christopher Browne 2005-06-30, 9:24 am |
| Tony Byrne wrote:
>Hi guys,
>
>Just a quick note to say that I encountered a small problem after I
>upgraded to Slony1 1.1.0. On trying to create a new set slonik would
>segfault and coredump. I solved the problem by adding a comment
>attribute in my 'create set' command, but surely it's legal not to
>specify a comment for a set?
>
>
Not to beat up on you at all; it would be appreciated if people
presenting such issues could record the (perceived :-)) bug at GBorg...
http://gborg.postgresql.org/project...ugs/buglist.php
It makes it way easier to track them, diminishing the likelihood that
someone will miss it due to the not-perfect-reliability of email.
Evidently things don't work out well if you don't specify a comment;
that indeed probably should be changed...
|
|
|
|
|