Prev: [HACKERS] Dividing progress/debug information in pg_standby, and stat before copy
Next: [HACKERS] C function accepting/returning cstring vs. text
From: Josh Berkus on 25 Jan 2010 13:50 All, Please rename this thread. I think that several people to whom it's relevant aren't replying to it because of the deceptive name. Thanks. --Josh -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "Joshua D. Drake" on 25 Jan 2010 13:53 On Mon, 2010-01-25 at 10:50 -0800, Josh Berkus wrote: > All, > > Please rename this thread. I think that several people to whom it's > relevant aren't replying to it because of the deceptive name. Thanks. > Except that it is. This thread was about whether or not, Mammoth would be considered to be in core. Which is fairly independent of the clustering docs. My suggestion would be to start a new thread entirely. Joshua D. Drake > --Josh > -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564 Consulting, Training, Support, Custom Development, Engineering Respect is earned, not gained through arbitrary and repetitive use or Mr. or Sir. -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Greg Smith on 25 Jan 2010 15:40 Joshua D. Drake wrote: > My suggestion would be to start a new thread entirely. > And mine would be to drop this whole topic altogether until after the CommitFest is over, and instead focus on the replication features already committed that need work before beta can even start. Only reason I said something is that I objected to the idea that the information on the wiki was complete enough to be considered a roadmap for others to follow in this area and wanted to clarify that it wasn't--it's helpful, but everybody knows it still needs work yet. Actually improving things enough that it is, that work I think is well outside of what this list should be focusing on right now. We've got pgsql-cluster-hackers to discuss this particular area. -- Greg Smith 2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support greg(a)2ndQuadrant.com www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Alvaro Herrera on 27 Jan 2010 14:21 Greg Smith wrote: > We've got pgsql-cluster-hackers to discuss this > particular area. Huh, is this a new list? It wasn't added to wwwmaster's list of lists, apparently, right? -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Greg Smith on 27 Jan 2010 14:24
Alvaro Herrera wrote: > Greg Smith wrote: > > >> We've got pgsql-cluster-hackers to discuss this >> particular area. >> > > Huh, is this a new list? It wasn't added to wwwmaster's list of lists, > apparently, right? > The archives are at http://archives.postgresql.org/pgsql-cluster-hackers/ but it's not listed at http://archives.postgresql.org/ for some reason. -- Greg Smith 2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support greg(a)2ndQuadrant.com www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |