[DOCS] Earliest Postgres credit patch
In reponse to Bruce's call for action on his blog, I spent my lunch hour doing a bit of transcription. Attached patch transcribes the list of Berkely students and staff who help write Postgres from Dr. Stonebraker's Turing Lecture: https://www.youtube.com/watch?v=BbGeKi6T6QI&feature=youtu.be&t=1h11m09s Ross -- Ross Reedstrom, Ph.D. reeds...@rice.edu Systems Engineer & Admin, Research Scientistphone: 713-348-6166 Connexions http://cnx.orgfax: 713-348-3665 Rice University MS-375, Houston, TX 77005 GPG Key fingerprint = F023 82C8 9B0E 2CC6 0D8E F888 D3AE 810E 88F0 BEDE diff --git a/doc/src/sgml/release-old.sgml b/doc/src/sgml/release-old.sgml index ec8e43f..07d5f57 100644 --- a/doc/src/sgml/release-old.sgml +++ b/doc/src/sgml/release-old.sgml @@ -6554,6 +6554,30 @@ The following bugs have been fixed in postgres95-beta-0.02: Initial release. + + +As reported by Dr. Michael Stonebraker, in his June 13, 2015 2014 ACM A.M. Turing Lecture: + +The Following 39 Berkeley Students and Staff + Wrote Postgres +(under the direction of Larry Rowe and myself) + +Jeff Alton, Paul Aoki, James Bell, Jennifer Caetta, +Philip Chang, Jolly Chen, Ron Choi, Matt Dillon, +Zelaine Fong, Adam Glass, Jeffrey Goh, Steven Grady, +Serge Granik, Marti Hearst, Joey Hellerstein, +Michael Hirohama, Chin-heng Hong, Wei Hong, +Anant Jhingren, Greg Kemnitz, Marcel Kornacker, +Case Larsen, Boris Livshitz, Jeff Meredith, Ginger Ogle, +Mike Olson, Nels Olson, Lay-Peng Ong, Carol Paxson, +Avi Pfeffer, Spyros Potamianos, Sunita Surawagi, +David Muir Sharnoff, Mark Sullivan, Cimarron Taylor, +Marc Teitelbaum, Yongdong Wang, Kristen Wright, and +Andrew Yu + +Transcribed from https://www.youtube.com/watch?v=BbGeKi6T6QI&feature=youtu.be&t=1h11m09s";> +accessed on August 5, 2015 +
Re: [DOCS] Earliest Postgres credit patch
On 2015-08-05 20:17, Ross Reedstrom wrote: In reponse to Bruce's call for action on his blog, I spent my lunch hour doing a bit of transcription. Attached patch transcribes the list of Berkely students and staff who help write Postgres from Dr. Stonebraker's Turing Lecture: https://www.youtube.com/watch?v=BbGeKi6T6QI&feature=youtu.be&t=1h11m09s (tentative, google-based) emendations: s/Chin-heng/Chin-Heng/ s/Jhingren/Jhingran/ s/Boris Livshitz/Boris Livshutz/ Also, those consecutive years: '2015 2014' on the first line are rather hard to read; a paraphrase would be good. Thanks, Erik Rijkers -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] Earliest Postgres credit patch
On Wed, Aug 05, 2015 at 08:45:16PM +0200, er wrote: > On 2015-08-05 20:17, Ross Reedstrom wrote: > >In reponse to Bruce's call for action on his blog, I spent my > >lunch hour doing > >a bit of transcription. Attached patch transcribes the list of > >Berkely students > >and staff who help write Postgres from Dr. Stonebraker's Turing > >Lecture: > > > >https://www.youtube.com/watch?v=BbGeKi6T6QI&feature=youtu.be&t=1h11m09s > > > > (tentative, google-based) emendations: > > s/Chin-heng/Chin-Heng/ > s/Jhingren/Jhingran/ > s/Boris Livshitz/Boris Livshutz/ Hmm, the problem here, is that the patch is an accurate transcription of a slide in the talk (seen at the timepoint at that URL - no need to scrub at all) should either add ibid. or edit brackets, or ...? The first is a case difference/alternate transcription. Stonebraker's list of publications does support the first two changes. The last, in particular, is wrong: I find 1993 vintage email threads (on GRASS) w/ a sigblock: -Boris Livshitz Postgres Group UC-Berkeley, Computer Science > > Also, those consecutive years: '2015 2014' on the first line are > rather hard to read; a paraphrase would be good. Yeah, probably: As reported by Dr. Michael Stonebraker, 2014 ACM A.M. Turing Lecture, delivered June 13, 2015 (amended): Amended attached. Ross > > Thanks, > > Erik Rijkers > > > > -- > Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-docs > -- Ross Reedstrom, Ph.D. reeds...@rice.edu Systems Engineer & Admin, Research Scientistphone: 713-348-6166 Connexions http://cnx.orgfax: 713-348-3665 Rice University MS-375, Houston, TX 77005 GPG Key fingerprint = F023 82C8 9B0E 2CC6 0D8E F888 D3AE 810E 88F0 BEDE diff --git a/doc/src/sgml/release-old.sgml b/doc/src/sgml/release-old.sgml index ec8e43f..db87e93 100644 --- a/doc/src/sgml/release-old.sgml +++ b/doc/src/sgml/release-old.sgml @@ -6554,6 +6554,31 @@ The following bugs have been fixed in postgres95-beta-0.02: Initial release. + + +As reported by Dr. Michael Stonebraker, in his ACM A.M. Turing Lecture, +delivered on June 13, 2015 2014 (amended): + +The Following 39 Berkeley Students and Staff + Wrote Postgres +(under the direction of Larry Rowe and myself) + +Jeff Alton, Paul Aoki, James Bell, Jennifer Caetta, +Philip Chang, Jolly Chen, Ron Choi, Matt Dillon, +Zelaine Fong, Adam Glass, Jeffrey Goh, Steven Grady, +Serge Granik, Marti Hearst, Joey Hellerstein, +Michael Hirohama, Chin-Heng Hong, Wei Hong, +Anant Jhingran, Greg Kemnitz, Marcel Kornacker, +Case Larsen, Boris Livshitz, Jeff Meredith, Ginger Ogle, +Mike Olson, Nels Olson, Lay-Peng Ong, Carol Paxson, +Avi Pfeffer, Spyros Potamianos, Sunita Surawagi, +David Muir Sharnoff, Mark Sullivan, Cimarron Taylor, +Marc Teitelbaum, Yongdong Wang, Kristen Wright, and +Andrew Yu + +Transcribed from https://www.youtube.com/watch?v=BbGeKi6T6QI&feature=youtu.be&t=1h11m09s";> +accessed on August 5, 2015 +
Re: [DOCS] Earliest Postgres credit patch
The last, in particular, is wrong: I find 1993 vintage email threads (on GRASS) w/ a sigblock: -Boris Livshitz Postgres Group UC-Berkeley, Computer Science Oh ok, I had forgotten the text was up there in the video. Fair enough. Then again, I found this: https://www.linkedin.com/in/livshutz Seems to be the same person. I guess it doesn't matter too much. Thanks, Erik Rijkers -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] max_worker_processes on the standby
On 2015-08-05 00:13, Alvaro Herrera wrote: Robert Haas wrote: On Tue, Aug 4, 2015 at 12:41 AM, Alvaro Herrera wrote: The alternative is to turn the feature on automatically if it sees that the master also has it on, i.e. the value would not be what the config file says it is. Doing this would be a bit surprising IMO, but given the behavior above maybe it's better than the current behavior. I think it's totally reasonable for the standby to follow the master's behavior rather than the config file. That should be documented, but otherwise, no problem. If it were technologically possible for the standby to follow the config file rather than the master in all cases, that would be fine, too. But the current behavior is somewhere in the middle, and that doesn't seem like a good plan. So I discussed this with Petr. He points out that if we make the standby follows the master, then the problem would be the misbehavior that results once the standby is promoted: at that point the standby would no longer "follow the master" and would start with the feature turned off, which could be disastrous (depending on what are you using the commit timestamps for). Given this, we're leaning towards the idea that the standby should not try to follow the master at all. Instead, an extension that wants to use this stuff can check the value for itself, and raise a fatal error if it's not already turned on the config file. That way, a lot of the strange corner cases disappear. Actually, after thinking bit more about this I think the behavior of these two will be similar - you suddenly lose the commit timestamp info. The difference is that with fist option you'll lose it after restart while with second one you lose it immediately after promotion since there was never any info on the slave. Extensions can do sanity checking in both scenarios. The way I see it the first option has following advantages: - it's smaller change - it's more consistent with how wal_log_hints behaves - fixing the config does not require server restart since the in-memory state was set from WAL record automatically However the second option has also some: - one can have slave which doesn't have overhead of the commit timestamp SLRU if they don't need it there - it's theoretically easier to notice that the track_commit_timestamps is off in config because the the SQL interface will complain if called on the slave So +0.5 from me towards following master and removing the error message -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] Using '>' in docs
On Thu, Jun 11, 2015 at 10:53:51PM -0400, Bruce Momjian wrote: > On Thu, Jun 11, 2015 at 10:51:25PM -0400, Tom Lane wrote: > > Bruce Momjian writes: > > > I see 34 instance of "=>" in our docs. Shouldn't the '>' be escaped, > > > e.g. =>? > > > > In principle, yes, though you can often get away with this as long as > > there's not a '<' nearby ... > > Yeah, that's what I thought --- it seems sloppy. What I am not clear > about is how to find other cases. Done. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
