Re: First SVG graphic
On 24/01/2019 00:53, Bruce Momjian wrote: > This is a pretty complicated issue with a lot of back-story. I am > thinking Tatsuo or me will probably commit it before March. Isn't that all the more reason to add it to the commitfest? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
couldn't find the tutorial sql's
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/11/sql.html Description: Hello PostgreSQL Team, as the title says, i couldn't find the SQL Scripts like basics.sql and advanced.sql after creating "mydb" to test it out. There was no such folder called tutorial or path ...src/tutorial/ on the system. Maybe you can help me with this. Sincerely, R. Classen
Re: First SVG graphic
On Fri, Jan 25, 2019 at 10:39:28AM +0100, Peter Eisentraut wrote: > On 24/01/2019 00:53, Bruce Momjian wrote: > > This is a pretty complicated issue with a lot of back-story. I am > > thinking Tatsuo or me will probably commit it before March. > > Isn't that all the more reason to add it to the commitfest? Uh, if you think so. Please add it then. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
Re: Release note trimming: another modest proposal
On Mon, Jan 7, 2019 at 09:18:29PM -0500, Jonathan Katz wrote: > So circling back on this, Peter's point makes a lot of sense. > > If you want to see release notes for other major versions, there would > be URLs to the other major versions, but that would be far less costly > than keeping the actual release notes in each tarball. I assume this means we would only keep the current release notes in the git tree too, e.g. 11.0, 11.1, 11.2, etc. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
Re: Release note trimming: another modest proposal
Bruce Momjian writes: > I assume this means we would only keep the current release notes in the > git tree too, e.g. 11.0, 11.1, 11.2, etc. Yeah, I'd imagine that each branch would have just its own release notes. I'm not sure whether to apply this policy retroactively to the supported back branches or just establish it going forward. Maintaining the notes could be pretty confusing for the next few years if we do the latter, though. regards, tom lane
Re: Release note trimming: another modest proposal
On Fri, Jan 25, 2019 at 06:41:20PM -0500, Tom Lane wrote: > Bruce Momjian writes: > > I assume this means we would only keep the current release notes in the > > git tree too, e.g. 11.0, 11.1, 11.2, etc. > > Yeah, I'd imagine that each branch would have just its own release notes. > > I'm not sure whether to apply this policy retroactively to the supported > back branches or just establish it going forward. Maintaining the notes > could be pretty confusing for the next few years if we do the latter, > though. Agreed. We would need to backpatch. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
Re: First SVG graphic
> On 24/01/2019 00:53, Bruce Momjian wrote: >> This is a pretty complicated issue with a lot of back-story. I am >> thinking Tatsuo or me will probably commit it before March. > > Isn't that all the more reason to add it to the commitfest? +1. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp
