On Sat, Jul 4, 2009 at 12:22 AM, Pavel Stehule<pavel.stehule@gmail.com> wrote:
> 2009/7/4 Scott Marlowe <scott.marlowe@gmail.com>:
>> On Sat, Jul 4, 2009 at 12:12 AM, Pavel Stehule<pavel.stehule@gmail.com> wrote:
>>> 2009/7/4 Scott Marlowe <scott.marlowe@gmail.com>:
>>>> On Fri, Jul 3, 2009 at 10:40 PM, Pavel Stehule<pavel.stehule@gmail.com> wrote:
>>>>> 2009/7/4 Roseller A. Romanos <don2_907@yahoo.com>:
>>>>>> Hi,
>>>>>>
>>>>>> I really have a serious problem with this. I hope you could give me some
>>>>>> insights on how to possibly solve this problem. I have installed a new copy
>>>>>> of postgres in my PC using Windows XP OS and I have copy the data folder in
>>>>>> my previous installation from the other PC, my problem is that I cannot
>>>>>> access the records that I have copied from the other PC.
>>>>>
>>>>> you cannot copy postgres data files from one computer to second.
>>>>> PostgreSQL is not MySQL. Use pg_dump instead or copy statement.
>>>>
>>>> Well, strictly speaking, if they're from the same architecture, with
>>>> the same compile time options and the same major version of pgsql*
>>>> then you can. But you need to shut down the source and destination
>>>> servers while doing it.
>>>
>>> and all your DDL operation are same and executed in same order too
>>
>> I'm not sure what you mean. If you shut down both db instances, and
>> copy the files over, there's no DDL involved really.
>>
>
> When you copy all files, then ok. But when you copy only one data
> file, then you have a problem.
>
> Problem should be different oid of pg_class table
Definitely, all files, and blow away the destination first. The OP
had said he copied the data directory, which should be more than
enough, but if they left old files in place I'm not so sure.
