Josh Berkus writes:
> 2) One reason users are using the "test -f" version of the archive
> command is that we put it in the same postgresql.conf. I would suggest
> that we don't put *any* archive command in the sample postgresql.conf,
> since there is no command we can supply which isn't a potent
On Mon, Aug 18, 2014 at 7:12 PM, Josh Berkus wrote:
> Magnus, Kevin:
>
> Two things:
>
> 1) pg_receivexlog doesn't help for users who need to archive from the
> master to cold storage (e.g. remote SAN, S3, whatever). So we're going
> to still need an archive_command.
It can, but it's definitely
Forwarding this to pgsql-jdbc mailing list.
On 08/18/2014 06:18 AM, Christopher Barham wrote:
> Hi,
>
>
>
> Just spotted a possible issue in the Documentation around loading the
> JDBC driver. This page documents how:
> http://jdbc.postgresql.org/documentation/93/load.html
>
> However, as of
Magnus, Kevin:
Two things:
1) pg_receivexlog doesn't help for users who need to archive from the
master to cold storage (e.g. remote SAN, S3, whatever). So we're going
to still need an archive_command.
2) One reason users are using the "test -f" version of the archive
command is that we put it
Hi,
Just spotted a possible issue in the Documentation around loading the JDBC
driver. This page documents how:
http://jdbc.postgresql.org/documentation/93/load.html
However, as of JDK6/JDBC 4.0, it should not be necessary to use the
Class.forName("org.postgresql.Driver");
method to load the JD
