question, converting version 11 sgml files at once.
Hi. I checked new version 11 doc files. at git.postgresql.org 2017-11-23 Peter Eisentraut Convert documentation to DocBook XML 2017-10-20 Peter Eisentraut Convert SGML IDs to lower case 2017-10-17 Peter Eisentraut Don't use SGML empty tags there were these commit log. I knew today that all sgml files have changed with these commit. I want to change korean sgml files too. How can I change all file at once? I tried with sed, perl, even if python sgml parser coding, unfortunately this work was not easy. Please let me know secret method :)
Doc creation failed (v10.5 & 11)
Hi, I have followed the following steps but I have failed to create the doc for PG11. cd .../postgresql-11 ./configure cd ../postgresql-11/doc/src/sgml make check I get the following error: make: *** No rule to make target '/configure', needed by 'version.sgml'. Stop. Any advice. Tia
Re: Doc creation failed (v10.5 & 11)
GPT writes: > I have followed the following steps but I have failed to create the > doc for PG11. > cd .../postgresql-11 > ./configure > cd ../postgresql-11/doc/src/sgml The above seems a bit confused. Are you trying to do a VPATH build? If so, you need to run configure in the build tree, not the source tree. That is, I'd have expected something more like cd ...buildtree... ../sourcetree/configure cd doc/src/sgml > make check You probably want "make" or "make all"; "make check" won't actually build anything. However, that's not related to this problem: > I get the following error: > make: *** No rule to make target '/configure', needed by 'version.sgml'. > Stop. Looking at the makefile, it's clear that $(top_srcdir) is expanding to empty. I'm not quite seeing how Makefile.global would end up doing that, but perhaps it's confused about vpath vs regular build. Another theory is that configure went wrong somehow and inserted bogus values into Makefile.global; was there any sign of distress while running configure? regards, tom lane
Re: Doc creation failed (v10.5 & 11)
Hi, thanks for the response. First of all I am a simple user who likes reading only the different content of the manual every time a new version comes up. So, what I want to do is to create the pg11.html file, next pg11.text file to compare it with pg10.x.text file (pg.org unfortunately stopped providing text files). The method I have followed is the same with that I did for 10.3 & 10.4. But it didn't work for 10.5 and now for 11. What I get is: config.status: ... yes|ok|no|other (no warning, no error) ... sed: -e expression #1, char 404: unknown option to `s' config.status: creating src/Makefile.global (file size zero "0" ie empty!) sed: -e expression #1, char 420: unknown option to `s' ... config.status: ... (no warning, no error) I am trying to build only the html and text documentation files. I have been following the instructions given in "J.3. Building The Documentation". Please, if possible, advise accurate instructions for newbiees! Tia On 10/19/18, Tom Lane wrote: > GPT writes: >> I have followed the following steps but I have failed to create the >> doc for PG11. > >> cd .../postgresql-11 >> ./configure >> cd ../postgresql-11/doc/src/sgml > > The above seems a bit confused. Are you trying to do a VPATH build? > If so, you need to run configure in the build tree, not the source tree. > That is, I'd have expected something more like > > cd ...buildtree... > ../sourcetree/configure > cd doc/src/sgml > >> make check > > You probably want "make" or "make all"; "make check" won't actually > build anything. However, that's not related to this problem: > >> I get the following error: >> make: *** No rule to make target '/configure', needed by 'version.sgml'. >> Stop. > > Looking at the makefile, it's clear that $(top_srcdir) is expanding > to empty. I'm not quite seeing how Makefile.global would end up > doing that, but perhaps it's confused about vpath vs regular build. > Another theory is that configure went wrong somehow and inserted > bogus values into Makefile.global; was there any sign of distress > while running configure? > > regards, tom lane >
The DROP TABLE instruction should have a TEMP option for when a temporary table
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/9.3/static/sql-createtable.html Description: Hi, There is an obvious "issue" with temporary tables. Case description: We have a public table public."myTooImportantTable" Then you have a temporary table: ;CREATE TEMP TABLE "myTooImportantTable" The issue is related to the intention of drop the temporary table: ;DROP TABLE "myTooImportantTable" -- <--- this drop the "myTooImportantTable" ;DROP TABLE "myTooImportantTable" -- <--- this drop the public."myTooImportantTable"
Re: The DROP TABLE instruction should have a TEMP option for when a temporary table
=?utf-8?q?PG_Doc_comments_form?= writes: > The issue is related to the intention of drop the temporary table: > ;DROP TABLE "myTooImportantTable" -- <--- this drop the > "myTooImportantTable" > ;DROP TABLE "myTooImportantTable" -- <--- this drop the > public."myTooImportantTable" If you want to be sure you drop a temp table and not a regular one, say DROP TABLE pg_temp.mytable; There's no need for new syntax. regards, tom lane
