> I'm quite sure that the schema change will not hurt nothing. However I have to
> say that add come column, with default value and a check on it is no to
> doable with very bigtables. Fortunately with the 8.0 you can do these tasks
> in one shot.
I've got a few 30GB tables anxiously awaiting th
Jan Wieck wrote:
> On 9/1/2004 9:02 PM, Gaetano Mendola wrote:
>
>> Jan Wieck wrote:
>>
>>
>>> Which is another point I was about to ask. How do these people,
>>> running those huge and horribly important databases, ever test a
>>> single application change? Or any schema changes for that matter. D
On 9/1/2004 9:02 PM, Gaetano Mendola wrote:
Jan Wieck wrote:
Which is another point I was about to ask. How do these people, running
those huge and horribly important databases, ever test a single
application change? Or any schema changes for that matter. Do they
really type "psql -c 'alter tab
Jan Wieck wrote:
Which is another point I was about to ask. How do these people, running
those huge and horribly important databases, ever test a single
application change? Or any schema changes for that matter. Do they
really type "psql -c 'alter table ...' proddb" and believe they are
profes
On Wed, 2004-09-01 at 13:50, Jan Wieck wrote:
> On 9/1/2004 1:51 PM, Serguei A. Mokhov wrote:
>
> > Date: Tue, 31 Aug 2004 23:35:18 -0400
> >
> > On 8/31/2004 9:38 PM, Andrew Rawnsley wrote:
> >
> >> On Aug 31, 2004, at 6:23 PM, Marc G. Fournier wrote:
> >>
> >>> On Tue, 31 Aug 2004, Josh Berkus
On 9/1/2004 1:51 PM, Serguei A. Mokhov wrote:
Date: Tue, 31 Aug 2004 23:35:18 -0400
On 8/31/2004 9:38 PM, Andrew Rawnsley wrote:
On Aug 31, 2004, at 6:23 PM, Marc G. Fournier wrote:
On Tue, 31 Aug 2004, Josh Berkus wrote:
Andrew,
If I were loony enough to want to make an attempt at a version
update
Date: Tue, 31 Aug 2004 23:35:18 -0400
On 8/31/2004 9:38 PM, Andrew Rawnsley wrote:
> On Aug 31, 2004, at 6:23 PM, Marc G. Fournier wrote:
>
>> On Tue, 31 Aug 2004, Josh Berkus wrote:
>>
>>> Andrew,
>>>
If I were loony enough to want to make an attempt at a version
updater
(i.e. mig
On Sep 1, 2004, at 12:19 PM, Josh Berkus wrote:
From my perspective, anyone who is running a 100GB,
can't-be-down-for-a-day
database and does not have more than 100GB free and/or a hot swap
server has
some *serious* priority problems.
Well, 100GB maybe excessive for this example. but I'm sure the
On Wed, Sep 01, 2004 at 09:47:02AM -0400, Jeff wrote:
>
> On Aug 31, 2004, at 6:30 PM, Josh Berkus wrote:
>
> >Huh? You can replicate onto the same server. Kicks your
> >performance in the teeth but it works fine. Heck, I did it on my
> >laptop as a demo.
>
> Doesn't work If you have say, a 1
Folks,
> Doesn't work If you have say, a 100GB db and only 50GB free space.
> Not nearly enough to duplicate. But plenty of breathing room for normal
> operation.
>From my perspective, anyone who is running a 100GB, can't-be-down-for-a-day
database and does not have more than 100GB free and/or a
On K, 2004-09-01 at 01:30, Josh Berkus wrote:
> Marc,
>
> > Slony is not an upgrade utility, and falls short in one big case ..
> > literally .. a very large database with limited cash resources to
> > duplicate it (as far as hardware is concerned). In small shops, or those
> > with 'free budget'
On Wed, 1 Sep 2004, Jan Wieck wrote:
On 9/1/2004 10:29 AM, Joe Conway wrote:
Jeff wrote:
On Aug 31, 2004, at 6:30 PM, Josh Berkus wrote:
Huh?You can replicate onto the same server.Kicks your performance
in
the teeth but it works fine. Heck, I did it on my laptop as a demo.
Doesn't work I
On 9/1/2004 10:29 AM, Joe Conway wrote:
Jeff wrote:
On Aug 31, 2004, at 6:30 PM, Josh Berkus wrote:
Huh?You can replicate onto the same server.Kicks your
performance in
the teeth but it works fine. Heck, I did it on my laptop as a demo.
Doesn't work If you have say, a 100GB db and only 5
Jeff wrote:
On Aug 31, 2004, at 6:30 PM, Josh Berkus wrote:
Huh?You can replicate onto the same server.Kicks your
performance in
the teeth but it works fine. Heck, I did it on my laptop as a demo.
Doesn't work If you have say, a 100GB db and only 50GB free space.
Not nearly enough to dup
On Aug 31, 2004, at 6:30 PM, Josh Berkus wrote:
Huh?You can replicate onto the same server.Kicks your
performance in
the teeth but it works fine. Heck, I did it on my laptop as a demo.
Doesn't work If you have say, a 100GB db and only 50GB free space.
Not nearly enough to duplicate. But
On Aug 31, 2004, at 11:35 PM, Jan Wieck wrote:
On 8/31/2004 9:38 PM, Andrew Rawnsley wrote:
On Aug 31, 2004, at 6:23 PM, Marc G. Fournier wrote:
On Tue, 31 Aug 2004, Josh Berkus wrote:
Andrew,
If I were loony enough to want to make an attempt at a version
updater
(i.e. migrate a
7.4 database to 8
On 8/31/2004 9:38 PM, Andrew Rawnsley wrote:
On Aug 31, 2004, at 6:23 PM, Marc G. Fournier wrote:
On Tue, 31 Aug 2004, Josh Berkus wrote:
Andrew,
If I were loony enough to want to make an attempt at a version
updater
(i.e. migrate a
7.4 database to 8.0 without an initdb), any suggestions on where
On Aug 31, 2004, at 6:23 PM, Marc G. Fournier wrote:
On Tue, 31 Aug 2004, Josh Berkus wrote:
Andrew,
If I were loony enough to want to make an attempt at a version
updater
(i.e. migrate a
7.4 database to 8.0 without an initdb), any suggestions on where to
poke first? Does a
catalog/list of system
Marc,
> Slony is not an upgrade utility, and falls short in one big case ..
> literally .. a very large database with limited cash resources to
> duplicate it (as far as hardware is concerned). In small shops, or those
> with 'free budget', Slony is perfect ... but if you are in an organization
>
On Tue, 31 Aug 2004, Josh Berkus wrote:
Andrew,
If I were loony enough to want to make an attempt at a version updater
(i.e. migrate a
7.4 database to 8.0 without an initdb), any suggestions on where to
poke first? Does a
catalog/list of system catalog changes exist anywhere? Any really gross
probl
Andrew,
> If I were loony enough to want to make an attempt at a version updater
> (i.e. migrate a
> 7.4 database to 8.0 without an initdb), any suggestions on where to
> poke first? Does a
> catalog/list of system catalog changes exist anywhere? Any really gross
> problems immediately
> present t
Andrew Rawnsley <[EMAIL PROTECTED]> writes:
> If I were loony enough to want to make an attempt at a version updater
> (i.e. migrate a 7.4 database to 8.0 without an initdb), any
> suggestions on where to poke first?
pg_upgrade is the way to go IMHO. I would not try to "dust off" the old
shell-sc
If I were loony enough to want to make an attempt at a version updater
(i.e. migrate a
7.4 database to 8.0 without an initdb), any suggestions on where to
poke first? Does a
catalog/list of system catalog changes exist anywhere? Any really gross
problems immediately
present themselves? Is dustin
23 matches
Mail list logo
