Bruce Momjian wrote:
Andrew Dunstan wrote:
[EMAIL PROTECTED] wrote:
I notice that PITR doesn't function correctly on Windows. Has that been
reported elsewhere?
The archive_command parameter %p resolves to a full path containing slashes
rather than backslashes. This is not a Windows file, so
Gaetano Mendola wrote:
Bruce Momjian wrote:
Yes, the fix will be in beta2 or the next pginstaller release.
Do you mean that the next pginstaller release will carry a 8.0beta1
with different behaviour that actual 8.0beta1 ?
I hope I mistake you.
What are you talking about? The installer project
Andrew Dunstan wrote:
Gaetano Mendola wrote:
Bruce Momjian wrote:
Yes, the fix will be in beta2 or the next pginstaller release.
Do you mean that the next pginstaller release will carry a 8.0beta1
with different behaviour that actual 8.0beta1 ?
I hope I mistake you.
What are you talking about?
Gaetano Mendola wrote:
BTW other projects are carrying also a build version in order to
distinguish
between two 8.0beta1 versions.
Except that we don't officially publish builds, only source sets.
Actually, this might be a reson to chenge to a different SCC system -
svn at least has a unique
I notice that PITR doesn't function correctly on Windows. Has that been
reported elsewhere?
The archive_command parameter %p resolves to a full path containing slashes
rather than backslashes. This is not a Windows file, so any attempt to copy
it fails. There isn't any way to avoid that.
I'm
[EMAIL PROTECTED] wrote:
I notice that PITR doesn't function correctly on Windows. Has that been
reported elsewhere?
The archive_command parameter %p resolves to a full path containing slashes
rather than backslashes. This is not a Windows file, so any attempt to copy
it fails. There isn't any
Andrew Dunstan wrote:
[EMAIL PROTECTED] wrote:
I notice that PITR doesn't function correctly on Windows. Has that been
reported elsewhere?
The archive_command parameter %p resolves to a full path containing slashes
rather than backslashes. This is not a Windows file, so any attempt to