bruce wrote:
> Tom Lane wrote:
> > Bruce Momjian writes:
> > > Tom Lane wrote:
> > >> (Come to think of it, --link can fail on Unix too, if the user tries to
> > >> put the new database on a different filesystem. Have you got guards in
> > >> there to make sure this is discovered before the point
Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian writes:
> > > pg_migrator needs hard link() capabiity on Win32 to support its --link
> > > option. Can someone create that and hopefully add it to libpgport?
> >
> > AFAIK hard links simply don't exist on Windows.
>
> Magnus showed me th
Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian writes:
> > > Tom Lane wrote:
> > >> (Come to think of it, --link can fail on Unix too, if the user tries to
> > >> put the new database on a different filesystem. Have you got guards in
> > >> there to make sure this is discovered before t
Tom Lane wrote:
> Bruce Momjian writes:
> > Tom Lane wrote:
> >> (Come to think of it, --link can fail on Unix too, if the user tries to
> >> put the new database on a different filesystem. Have you got guards in
> >> there to make sure this is discovered before the point of no return?)
>
> > Of
Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian writes:
> > > Tom Lane wrote:
> > >> AFAIK hard links simply don't exist on Windows.
> >
> > > Magnus showed me this:
> > > http://msdn.microsoft.com/en-us/library/aa363860(VS.85).aspx
> >
> > Hmm, interesting. Are we requiring our DBs
Bruce Momjian writes:
> Tom Lane wrote:
>> (Come to think of it, --link can fail on Unix too, if the user tries to
>> put the new database on a different filesystem. Have you got guards in
>> there to make sure this is discovered before the point of no return?)
> Of course:
> ...
> though you ha
Tom Lane wrote:
> Bruce Momjian writes:
> >> Tom Lane wrote:
> >>> Hmm, interesting. Are we requiring our DBs to be on NTFS already?
>
> > Oh, yea, we only support tablespaces on Win32 using NTFS.
>
> Well, the important point there is that we fail gracefully if you try to
> use tablespaces whe
Bruce Momjian writes:
>> Tom Lane wrote:
>>> Hmm, interesting. Are we requiring our DBs to be on NTFS already?
> Oh, yea, we only support tablespaces on Win32 using NTFS.
Well, the important point there is that we fail gracefully if you try to
use tablespaces when not on NTFS. So you're going
Tom Lane wrote:
> Bruce Momjian writes:
> > Tom Lane wrote:
> >> AFAIK hard links simply don't exist on Windows.
>
> > Magnus showed me this:
> > http://msdn.microsoft.com/en-us/library/aa363860(VS.85).aspx
>
> Hmm, interesting. Are we requiring our DBs to be on NTFS already?
I think we re
Bruce Momjian writes:
> Tom Lane wrote:
>> AFAIK hard links simply don't exist on Windows.
> Magnus showed me this:
> http://msdn.microsoft.com/en-us/library/aa363860(VS.85).aspx
Hmm, interesting. Are we requiring our DBs to be on NTFS already?
What are the implications for Cygwin?
Bruce Momjian wrote:
> pg_migrator needs hard link() capabiity on Win32 to support its --link
> option. Can someone create that and hopefully add it to libpgport?
> libpgport currently only has symlink capability for Win32.
Can we use CreateHardLink() ?
http://msdn.microsoft.com/en-us/library
Tom Lane wrote:
> Bruce Momjian writes:
> > pg_migrator needs hard link() capabiity on Win32 to support its --link
> > option. Can someone create that and hopefully add it to libpgport?
>
> AFAIK hard links simply don't exist on Windows.
Magnus showed me this:
http://msdn.microsoft.co
Bruce Momjian writes:
> pg_migrator needs hard link() capabiity on Win32 to support its --link
> option. Can someone create that and hopefully add it to libpgport?
AFAIK hard links simply don't exist on Windows.
regards, tom lane
--
Sent via pgsql-hackers mailing list
pg_migrator needs hard link() capabiity on Win32 to support its --link
option. Can someone create that and hopefully add it to libpgport?
libpgport currently only has symlink capability for Win32.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://en
14 matches
Mail list logo
