Martijn van Oosterhout writes:
> The only issue I can think of is that constraints might be violated
> (duplicate keys in unique index) because one of the records might have
> been invisible when the second was created...
More generally, application-driven updates of derived data might be
wrong b
On Mon, Dec 26, 2005 at 04:11:49PM -0500, Jaime Casanova wrote:
> yes, it seems that's enough...
>
> i was trying to help to a buddy in the spanish list and my first
> recommendation was to copy all data directory... when he tries that he
> makes a vacuum and the data go back...
>
> i told him to
On 12/26/05, Martijn van Oosterhout wrote:
> On Mon, Dec 26, 2005 at 03:21:03PM -0500, Jaime Casanova wrote:
> > Hi, can someone point me where is explained how can i recover from a
> > wraparound that vanish all databases in a cluster?
>
> Some recent investigation indicates that simply doing a V
On Mon, Dec 26, 2005 at 03:21:03PM -0500, Jaime Casanova wrote:
> Hi, can someone point me where is explained how can i recover from a
> wraparound that vanish all databases in a cluster?
Some recent investigation indicates that simply doing a VACUUM on the
databases in question should bring the d
Hi, can someone point me where is explained how can i recover from a
wraparound that vanish all databases in a cluster?
--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
Tino Wildenhain <[EMAIL PROTECTED]> writes:
> Hehe, x-mas time ;) He said "dumping" and "restoring" on initial post.
> I was wondering too as you said it would not work.
I assumed he was hoping to take a shortcut, but maybe I was overthinking
the question ...
regards, tom
Tom Lane schrieb:
> Benjamin Arai <[EMAIL PROTECTED]> writes:
>
>>Is there a way to transfer data between the two architectures?
>
>
> Sure: pg_dump. But you can't just move the physical database files,
> any more than you could do across completely different architectures.
Hehe, x-mas time ;)
Oh, great. Thanks.
Tom Lane wrote:
Benjamin Arai <[EMAIL PROTECTED]> writes:
Is there a way to transfer data between the two architectures?
Sure: pg_dump. But you can't just move the physical database files,
any more than you could do across completely different archi
Benjamin Arai <[EMAIL PROTECTED]> writes:
> Is there a way to transfer data between the two architectures?
Sure: pg_dump. But you can't just move the physical database files,
any more than you could do across completely different architectures.
regards, tom lane
I thought you said that it would not work in either direction?
Joshua D. Drake wrote:
Benjamin
Arai wrote:
Is there a way to transfer data between the
two architectures?
I would think you could do it over the network:
pg_dump -U postgres foo|psql -U postgres -h other_mach
Benjamin Arai wrote:
> Is there a way to transfer data between the two architectures?
pg_dump.
---
>
> Tom Lane wrote:
>
> >Benjamin Arai <[EMAIL PROTECTED]> writes:
> >
> >
> >>Are there any compatability issues from d
Benjamin Arai wrote:
Is there a way to transfer data between the two architectures?
I would think you could do it over the network:
pg_dump -U postgres foo|psql -U postgres -h other_machine foo
Tom Lane wrote:
Benjamin Arai <[EMAIL PROTECTED]> writes:
Are there any compatability issues
Is there a way to transfer data between the two architectures?
Tom Lane wrote:
Benjamin Arai <[EMAIL PROTECTED]> writes:
Are there any compatability issues from dumping a database from a x86
installation and restoring it on a 64bit install or vice versa?
It won't work,
Benjamin Arai <[EMAIL PROTECTED]> writes:
> Are there any compatability issues from dumping a database from a x86
> installation and restoring it on a 64bit install or vice versa?
It won't work, in either direction, because of different alignment rules.
regards, tom lane
Are there any compatability issues from dumping a database from a x86
installation and restoring it on a 64bit install or vice versa? I am
assuming I can go from x86 to 64 but I am not sure about the other
way. Any information would be greatly appreciated.
--
Benjamin Arai
[EMAIL PROTECTED]
Joshua Kramer wrote:
>
> Greetings,
>
> Where in the documentation can I find information on the low-level
> behavior of triggers that fire as a result of insert/update statements
> inside of transactions?
>
> Do the triggers fire at the point the transaction is COMMITted? Or as
> soon as th
16 matches
Mail list logo