On Fri, Apr 18, 2008 at 11:15:09AM -0700, Joshua D. Drake wrote:
> sync transaction have to run? You know vacuum isn't working while
> that transaction is open right? Are you going to have to setup up a
> dozen different replicated sets in order to get it done?
A dozen sets isn't really a big de
On Sun, 20 Apr 2008, Scott Marlowe wrote:
I wonder if there's a comprehensive list somewhere...
There's a good list on the database side at
http://www.postgresql.org/docs/current/interactive/populate.html but it
doesn't dwelve into hardware changes. I put a reference to that as a
placehold
[EMAIL PROTECTED] (Csaba Nagy) writes:
> On Sun, 2008-04-20 at 11:32 -0600, Scott Marlowe wrote:
>> On Sun, Apr 20, 2008 at 11:12 AM, Scott Ribe <[EMAIL PROTECTED]> wrote:
>> > > I am going to play with this and see where it breaks, but it's going to
>> > > be
>> > > an enormous time investment t
On Sun, 2008-04-20 at 11:32 -0600, Scott Marlowe wrote:
> On Sun, Apr 20, 2008 at 11:12 AM, Scott Ribe <[EMAIL PROTECTED]> wrote:
> > > I am going to play with this and see where it breaks, but it's going to be
> > > an enormous time investment to babysit it.
One more suggestion: if you happen to
On Fri, Apr 18, 2008 at 9:04 PM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> On Fri, 18 Apr 2008 14:59:34 -0400
> Alvaro Herrera <[EMAIL PROTECTED]> wrote:
>
> > I find it pretty unlikely that Slony would be unable to help you
> > upgrade here. Obviously you can upgrade one database at a time.
On Sun, Apr 20, 2008 at 12:48 PM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> On Sun, 20 Apr 2008 11:32:58 -0600
> "Scott Marlowe" <[EMAIL PROTECTED]> wrote:
>
> > Exactly. There are several things you can do on the replica that you
> > wouldn't do on the master for better performance. Really
On Sun, 20 Apr 2008 11:32:58 -0600
"Scott Marlowe" <[EMAIL PROTECTED]> wrote:
> Exactly. There are several things you can do on the replica that you
> wouldn't do on the master for better performance. Really big numbers
> of WAL segments, no background writer, fsync off as mentioned, WAL on
> a
On Sun, Apr 20, 2008 at 11:12 AM, Scott Ribe <[EMAIL PROTECTED]> wrote:
> > I am going to play with this and see where it breaks, but it's going to be
> > an enormous time investment to babysit it.
>
> One thing to remember, since you've already got backup in place and this
> replica would just
> I am going to play with this and see where it breaks, but it's going to be
> an enormous time investment to babysit it.
One thing to remember, since you've already got backup in place and this
replica would just be for upgrading, not a hot spare, turn off fsync during
the initial subscription. M
On Apr 18, 2008, at 2:18 PM, Alvaro Herrera wrote:
Actually, electrons themselves flow rather slowly -- millimeters per
second according to Wikipedia. The signal propagation is a bit
faster:
"typically 75% of light speed", Wikipedia again.
Yeah, electrons move *very* slowly in a solid. Pre
On Apr 18, 2008, at 2:04 PM, Joshua D. Drake wrote:
On Fri, 18 Apr 2008 14:59:34 -0400
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
I find it pretty unlikely that Slony would be unable to help you
upgrade here. Obviously you can upgrade one database at a time.
Also, mostly it's not the database
Alvaro Herrera wrote:
Geoffrey wrote:
I'm really not altogether sure what you mean by transaction velocity.
I'm pretty sure the electrons are traveling pretty close to the speed of
light. ;)
Actually, electrons themselves flow rather slowly -- millimeters per
second according to Wikipedia.
Geoffrey wrote:
> I'm really not altogether sure what you mean by transaction velocity.
> I'm pretty sure the electrons are traveling pretty close to the speed of
> light. ;)
Actually, electrons themselves flow rather slowly -- millimeters per
second according to Wikipedia. The signal propag
Joshua D. Drake wrote:
> On Fri, 18 Apr 2008 14:59:34 -0400
> Alvaro Herrera <[EMAIL PROTECTED]> wrote:
>
> > I find it pretty unlikely that Slony would be unable to help you
> > upgrade here. Obviously you can upgrade one database at a time.
> >
> > Also, mostly it's not the database size what'
Joshua D. Drake wrote:
On Fri, 18 Apr 2008 14:59:34 -0400
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
I find it pretty unlikely that Slony would be unable to help you
upgrade here. Obviously you can upgrade one database at a time.
Also, mostly it's not the database size what's a concern, but ra
Alvaro Herrera wrote:
Geoffrey wrote:
Joshua D. Drake wrote:
On Fri, 18 Apr 2008 14:30:18 -0400
Geoffrey <[EMAIL PROTECTED]> wrote:
I don't know that slony is the answer. It was more of a question
then an answer. We are hoping to use that solution to migrate from
7.4.19 to 8.3.1. The prima
On Fri, 18 Apr 2008 14:59:34 -0400
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> I find it pretty unlikely that Slony would be unable to help you
> upgrade here. Obviously you can upgrade one database at a time.
>
> Also, mostly it's not the database size what's a concern, but rather
> the size of
Geoffrey wrote:
> Joshua D. Drake wrote:
>> On Fri, 18 Apr 2008 14:30:18 -0400
>> Geoffrey <[EMAIL PROTECTED]> wrote:
>>
>>> I don't know that slony is the answer. It was more of a question
>>> then an answer. We are hoping to use that solution to migrate from
>>> 7.4.19 to 8.3.1. The primary re
On Friday 18 April 2008, Geoffrey <[EMAIL PROTECTED]> wrote:
> What about the:
>
> 8.1 -> slony -> 8.3
> switch users to 8.3 databases
>
> solution.
15+ million row inserts/updates a day across 1000+ tables. Oh, and an
extensive existing Slony structure for some portions of the database.
I could
Joshua D. Drake wrote:
On Fri, 18 Apr 2008 14:30:18 -0400
Geoffrey <[EMAIL PROTECTED]> wrote:
I don't know that slony is the answer. It was more of a question
then an answer. We are hoping to use that solution to migrate from
7.4.19 to 8.3.1. The primary reason is to reduce downtime.
Well
On Fri, 18 Apr 2008 14:30:18 -0400
Geoffrey <[EMAIL PROTECTED]> wrote:
> I don't know that slony is the answer. It was more of a question
> then an answer. We are hoping to use that solution to migrate from
> 7.4.19 to 8.3.1. The primary reason is to reduce downtime.
Well :) That is why I aske
Joshua D. Drake wrote:
On Fri, 18 Apr 2008 13:54:52 -0400
Geoffrey <[EMAIL PROTECTED]> wrote:
What about the:
8.1 -> slony -> 8.3
switch users to 8.3 databases
solution.
Is it? What is your transactional velocity? How long will the initial
sync transaction have to run? You know vacuum isn't
On Fri, 18 Apr 2008 13:54:52 -0400
Geoffrey <[EMAIL PROTECTED]> wrote:
> What about the:
>
> 8.1 -> slony -> 8.3
> switch users to 8.3 databases
>
> solution.
Is it? What is your transactional velocity? How long will the initial
sync transaction have to run? You know vacuum isn't working while
Alan Hodgson wrote:
On Friday 18 April 2008, Chris Browne <[EMAIL PROTECTED]> wrote:
I note in the blog that the "in place upgrade" issue came up.
(Interesting to observe that it *also* came up pretty prominently in
the intro session at PG East... This is obviously a matter of Not
Inconsiderabl
On Friday 18 April 2008, Chris Browne <[EMAIL PROTECTED]> wrote:
> I note in the blog that the "in place upgrade" issue came up.
> (Interesting to observe that it *also* came up pretty prominently in
> the intro session at PG East... This is obviously a matter of Not
> Inconsiderable Interest...)
[EMAIL PROTECTED] ("Joshua D. Drake") writes:
> On Thu, 17 Apr 2008 22:19:23 -0500
> Josh Trutwin <[EMAIL PROTECTED]> wrote:
>
>> Is your presentation available online at all?
>
> Blogging the bad boy up right now Will be available soon.
The presentation seems pretty good...
... But what is
On Thu, 17 Apr 2008 16:43:04 -0400
Geoffrey <[EMAIL PROTECTED]> wrote:
> Joshua D. Drake wrote:
> > Hello,
> >
> > I am currently chilling at MySQLCon. If any other Elephant riders
> > who are doing a little Dolphin hunting are about... I am in
> > Ballroom E about to give a talk on what Mysql ca
On Thu, 17 Apr 2008 22:19:23 -0500
Josh Trutwin <[EMAIL PROTECTED]> wrote:
> Is your presentation available online at all?
Blogging the bad boy up right now Will be available soon.
Joshua D. Drake
--
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community
On Thu, 17 Apr 2008 11:29:56 -0700
"Joshua D. Drake" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I am currently chilling at MySQLCon. If any other Elephant riders
> who are doing a little Dolphin hunting are about... I am in
> Ballroom E about to give a talk on what Mysql can learn from
> PostgreSQL.
On Thu, Apr 17, 2008 at 11:29 AM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I am currently chilling at MySQLCon. If any other Elephant riders who
> are doing a little Dolphin hunting are about... I am in Ballroom E
> about to give a talk on what Mysql can learn from PostgreSQL.
is
Joshua D. Drake wrote:
Hello,
I am currently chilling at MySQLCon. If any other Elephant riders who
are doing a little Dolphin hunting are about... I am in Ballroom E
about to give a talk on what Mysql can learn from PostgreSQL.
Check the room for barrels of tar and feathers before you start y
Dude, you have got to let us know how that goes...
On Apr 17, 2008, at 1:29 PM, Joshua D. Drake wrote:
Hello,
I am currently chilling at MySQLCon. If any other Elephant riders who
are doing a little Dolphin hunting are about... I am in Ballroom E
about to give a talk on what Mysql can learn fro
Hello,
I am currently chilling at MySQLCon. If any other Elephant riders who
are doing a little Dolphin hunting are about... I am in Ballroom E
about to give a talk on what Mysql can learn from PostgreSQL.
Sincerely,
Joshua D. Drake
--
The PostgreSQL Company since 1997: http://www.commandpromp
33 matches
Mail list logo
