On Wed, Jan 20, 2010 at 7:30 AM, Josh Berkus wrote:
> So, here's a must-fix item for SR for release: we need adequate docs.
> I'm happy to write these but *I* need to understand the answers first.
Thanks a lot!
> The current docs and wiki page do not explain:
>
> * How (technically) the slave li
Josh Berkus wrote:
> So, here's a must-fix item for SR for release: we need adequate docs.
> I'm happy to write these but *I* need to understand the answers first.
Many thanks!
> The current docs and wiki page do not explain:
>
> * How (technically) the slave listens for LSNs
Hmm, not sure what
> Devrim gave you the wrong location. It is already installed where we put
> other samples like postgresql.conf.sample, namely $SHAREDIR.
>
> Nobody has to look in the source.
>
> I don't think initdb should copy it by default, many users won't want
> such an animal at all. Maybe an initdb switc
Josh Berkus wrote:
On 1/20/10 12:00 PM, Devrim GÜNDÜZ wrote:
On Wed, 2010-01-20 at 11:30 +1300, Josh Berkus wrote:
Also, given that recovery.conf has become a key part of our
replication, shouldn't we supply a recovery.example file which people
can rename and edit? Happy to write thi
On Wed, 2010-01-20 at 13:36 +1300, Josh Berkus wrote:
> Well, it doesn't get created in PGDATA, and the docs don't mention the
> above location that I could find.
It is installed under share/ directory for source installations. RPMs
install it under /usr/share/pgsql.
> Can we get initdb to copy
On 1/20/10 12:00 PM, Devrim GÜNDÜZ wrote:
> On Wed, 2010-01-20 at 11:30 +1300, Josh Berkus wrote:
>> Also, given that recovery.conf has become a key part of our
>> replication, shouldn't we supply a recovery.example file which people
>> can rename and edit? Happy to write this too.
>
> We ship i
On Wed, 2010-01-20 at 11:30 +1300, Josh Berkus wrote:
>
> Also, given that recovery.conf has become a key part of our
> replication, shouldn't we supply a recovery.example file which people
> can rename and edit? Happy to write this too.
We ship it already:
src/backend/access/transam/recovery.
Hackers,
So, here's a must-fix item for SR for release: we need adequate docs.
I'm happy to write these but *I* need to understand the answers first.
The current docs and wiki page do not explain:
* How (technically) the slave listens for LSNs
* Does the walreceiver need the archive (via archive
