Re: Dump from cygwin directly to windows
От | Mike G |
---|---|
Тема | Re: Dump from cygwin directly to windows |
Дата | |
Msg-id | 1103600303.5304.14.camel@localhost.localdomain обсуждение исходный текст |
Ответ на | Re: Dump from cygwin directly to windows (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
Ok, I didn't think you could do a restore as a non-superuser. I had executed the command on the remote(cygwin) machine in this case. I didn't specify a user to have it run as on the windows side (thought it would default to postgres). On the cygwin side I did execute it under a non-superuser domain account. When I first saw all the \N errors I thought it was a unix to windows end of line character conversion error. Thanks for your help. Mike On Sat, 2004-12-18 at 11:00, Tom Lane wrote: > Mike G <mike@thegodshalls.com> writes: > > It looks like it started off as a permissions problem. I added the > > users to the database before trying again and this time it worked fine. > > I have attached the log from the original attempt if you wish to have a > > look. > > As best I can tell, you ran the restore script as a non-superuser, which > probably wasn't a good thing to do. 8.0 pg_dump generates scripts that > should cope with this situation a bit more reasonably, but it would > still end up as a do-over in most cases because none of the object > ownerships would come out right. > > regards, tom lane
В списке pgsql-hackers по дате отправления: