About Portuguese language support of Text Search
Hello pgsql-docs team, I have a question to confirm with you. In this link https://www.postgresql.org/docs/10/textsearch-psql.html, pgsql mentions supporting multiple languages of Text Search, which includes Portuguese. What I want to confirm is that the supported Portuguese here including both Brazil Portuguese and Portugal Portuguese? Or just Portugal Portuguese? Thanks and looking forward to hearing from you. Cathy Huang
1.3. Creating a Database (on Windows) - User Experience
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/11/tutorial-createdb.html Description: Hi, I'm following your tutorial to learn PostgreSQL. When I try to create a database, I keep getting a "password authentication failed" error, that doesn't let me continue. The problem was not issued in the tutorial. I did a quick googling, and found that the problem was that postgres was installed as admin, so the pass I set up in the installation wizard was for the main admin account, "postgres". Maybe you could add that the solution is pretty simple, just do a: createdb -U postgres mydb, and it will work flawlessly. Thanks for the tutorial!
Typo in URL
URL of OASIS group has been changed from http://www.oasis-open.org/ to https://www.oasis-open.org/, but there's a place where http is still used. Attached patch fixes that. Best regards, -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp diff --git a/doc/src/sgml/docguide.sgml b/doc/src/sgml/docguide.sgml index aa0f278b02..0608b8c612 100644 --- a/doc/src/sgml/docguide.sgml +++ b/doc/src/sgml/docguide.sgml @@ -80,7 +80,7 @@ - http://www.oasis-open.org/docbook/";>DocBook DTD + https://www.oasis-open.org/docbook/";>DocBook DTD This is the definition of DocBook itself. We currently use version
Re: First SVG graphic
The attached patch contains all necessary changes to the sgml, svg, and Makefile. (Possibly we need some more changes regarding the 'install*' tasks of Makefile.) How to go on? Shall I send the patch to a different list or to Commitfest 2019-03? Kind regards Jürgen Purtz On 17.01.19 23:43, Tatsuo Ishii wrote: Thanks to an additional template created by Alexander Lakhin, which extends the 'nochunk' stylesheet for SVG and MathML processing, it is now possible to create the "single HTML file" of our documentation including SVG. For me this is a working solution as long as we use Docbook 4. After the migration to Docbook 5, both languages as well as full namespace support will be natively included in Docbook. Does anyone faced some more problems? Or can we start to include the three first SVG graphics into PG's documentation? OK, the wiki pages look good, as do the diagrams, and I think you have the process we all agreed with. Should we move ahead and commit some of these diagrams to the souce tree for PG 12? Yes, I think we should. Best regards, -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp diff --git a/doc/src/sgml/Makefile b/doc/src/sgml/Makefile index 8326c7c673..27d1e674f4 100644 --- a/doc/src/sgml/Makefile +++ b/doc/src/sgml/Makefile @@ -57,6 +57,8 @@ GENERATED_SGML = version.sgml \ ALLSGML := $(wildcard $(srcdir)/*.sgml $(srcdir)/ref/*.sgml) $(GENERATED_SGML) +SVGSRC := $(wildcard $(srcdir)/svg/*.svg) + ## ## Man pages @@ -125,10 +127,12 @@ endif html: html-stamp -html-stamp: stylesheet.xsl postgres.sgml $(ALLSGML) +html-stamp: stylesheet.xsl postgres.sgml $(ALLSGML) $(SVGSRC) $(XMLLINT) $(XMLINCLUDE) --noout --valid $(word 2,$^) $(XSLTPROC) $(XMLINCLUDE) $(XSLTPROCFLAGS) $(XSLTPROC_HTML_FLAGS) $(wordlist 1,2,$^) cp $(srcdir)/stylesheet.css html/ + $(MKDIR_P) html/svg + cp $(SVGSRC) html/svg touch $@ htmlhelp: stylesheet-hh.xsl postgres.sgml $(ALLSGML) @@ -136,7 +140,7 @@ htmlhelp: stylesheet-hh.xsl postgres.sgml $(ALLSGML) $(XSLTPROC) $(XMLINCLUDE) $(XSLTPROCFLAGS) $(wordlist 1,2,$^) # single-page HTML -postgres.html: stylesheet-html-nochunk.xsl postgres.sgml $(ALLSGML) +postgres.html: stylesheet-html-nochunk.xsl postgres.sgml $(ALLSGML) $(SVGSRC) $(XMLLINT) $(XMLINCLUDE) --noout --valid $(word 2,$^) $(XSLTPROC) $(XMLINCLUDE) $(XSLTPROCFLAGS) $(XSLTPROC_HTML_FLAGS) -o $@ $(wordlist 1,2,$^) @@ -152,15 +156,15 @@ postgres.txt: postgres.html postgres.pdf: $(error Invalid target; use postgres-A4.pdf or postgres-US.pdf as targets) -%-A4.fo: stylesheet-fo.xsl %.sgml $(ALLSGML) +%-A4.fo: stylesheet-fo.xsl %.sgml $(XMLLINT) $(XMLINCLUDE) --noout --valid $(word 2,$^) $(XSLTPROC) $(XMLINCLUDE) $(XSLTPROCFLAGS) --stringparam paper.type A4 -o $@ $(wordlist 1,2,$^) -%-US.fo: stylesheet-fo.xsl %.sgml $(ALLSGML) +%-US.fo: stylesheet-fo.xsl %.sgml $(XMLLINT) $(XMLINCLUDE) --noout --valid $(word 2,$^) $(XSLTPROC) $(XMLINCLUDE) $(XSLTPROCFLAGS) --stringparam paper.type USletter -o $@ $(wordlist 1,2,$^) -%.pdf: %.fo +%.pdf: %.fo $(ALLSGML) $(SVGSRC) $(FOP) -fo $< -pdf $@ @@ -169,7 +173,7 @@ postgres.pdf: ## epub: postgres.epub -postgres.epub: postgres.sgml $(ALLSGML) +postgres.epub: postgres.sgml $(ALLSGML) $(SVGSRC) $(XMLLINT) --noout --valid $< $(DBTOEPUB) $< @@ -209,7 +213,7 @@ check: postgres.sgml $(ALLSGML) check-tabs install: install-html install-man installdirs: - $(MKDIR_P) '$(DESTDIR)$(htmldir)'/html $(addprefix '$(DESTDIR)$(mandir)'/man, 1 3 $(sqlmansectnum)) + $(MKDIR_P) '$(DESTDIR)$(htmldir)'/html/svg html/svg $(addprefix '$(DESTDIR)$(mandir)'/man, 1 3 $(sqlmansectnum)) # If the install used a man directory shared with other applications, this will remove all files. uninstall: diff --git a/doc/src/sgml/gin.sgml b/doc/src/sgml/gin.sgml index cc7cd1ed2c..195e385798 100644 --- a/doc/src/sgml/gin.sgml +++ b/doc/src/sgml/gin.sgml @@ -453,6 +453,17 @@ key values for different columns can be of different types. + + + + + + + + + + + GIN Fast Update Technique diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index 9e0bb93f08..1fd9ced5f5 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -73,6 +73,17 @@ PostgreSQL documentation architectures. + + + + + + + + + + + When used with one of the archive file formats and combined with pg_restore, diff --git a/doc/src/sgml/storage.sgml b/doc/src/sgml/storage.sgml index 8ef2ac8010..4d39ceb958 100644 --- a/doc/src/sgml/storage.sgml +++ b/doc/src/sgml/storage.sgml @@ -775,6 +775,17 @@ data. Empty in ordinary tables. + + + + + + + + + + + The first 24 bytes of each page consists of a page header diff --git a/doc/src/sgml/stylesheet-html-nochunk.xsl b/doc/src/sgml/stylesheet-html-nochunk.xsl index ffd2012e91..9e756708f5 100644 -
Re: About Portuguese language support of Text Search
Black White writes: > I have a question to confirm with you. In this link > https://www.postgresql.org/docs/10/textsearch-psql.html, pgsql mentions > supporting multiple languages of Text Search, which includes Portuguese. > What I want to confirm is that the supported Portuguese here including both > Brazil Portuguese and Portugal Portuguese? Or just Portugal Portuguese? There's just one "portuguese" configuration in our standard set of text search configurations. The only things that are really language-specific about it are the Snowball stemmer (to discard uninteresting word terminations, such as plurals) and the stop-list of common words to ignore. It might be that neither of those are particularly specific to one dialect of Portuguese --- at least, the upstream Snowball code/docs don't seem to mention anything about that. In any case, you could create your own modified configuration if you don't like what the standard one does. The stopword list, in particular, is quite trivial to modify. regards, tom lane
Re: tickling the lesser contributor's withering ego
On 2018-Dec-27, Magnus Hagander wrote: > On Fri, Dec 21, 2018 at 4:17 PM Alvaro Herrera > wrote: > > > On 2018-Dec-21, Tom Lane wrote: > > > > > Alvaro Herrera writes: > > > > I propose the following patch, which will make those links stable -- > > > > then we can add the following links to the contributors page: > > > > https://www.postgresql/org/docs/10/release-10.html#RELEASE-10-ACKNOWLEDGEMENTS > > > > https://www.postgresql/org/docs/11/release-11.html#RELEASE-11-ACKNOWLEDGEMENTS > > > > > > Seems reasonable, but note the lag time --- unless somebody does > > > something out of the ordinary, those pages won't actually have > > > such tags till after the February minor releases. > > > > Good point. That seems acceptable to me. > > Good. While it *can* be worked around, it's a PITA and it risks getting > overwritten by other things, since the normal docs loads are based off > release tarballs. We can make them off a snapshot tarball, but it's a pain > :) > > Oh, and +1 for stable links like that in general. That would be one good > step. Okay, pushed this. There's no need to do any advance publishing I think; we can wait three more weeks. We still need Erik to come up with the patch for pgweb, though :-) -- Álvaro Herrerahttps://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Re: citext plugin is not working with java applications
On Mon, Dec 10, 2018 at 10:21:26AM +, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/citext.html > Description: > > The citext plugin does not work in combination with jdbc. Thus it does not > work with Java applications. It does work in pgadmin because that is python. > I am using the right schema, and setting the jdbc stringtype to unspecified > makes no difference. > Because Java is the most used programming language, a big warning on the > postgresql citext documentation > (https://www.postgresql.org/docs/10/citext.html) is needed until this is > fixed. > Case insensitive text is standard on many databases, thus this may be a big > obstacle when you want to migrate. You have not explained what "does not work" means. -- 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: citext plugin is not working with java applications
On Mon, Jan 21, 2019 at 7:39 PM Bruce Momjian wrote: > You have not explained what "does not work" means. True...but assuming it is true would we accept placing a driver-specific warning here? We do not do so anywhere else in the documentation that I am aware. The main issue, IIUC, is that Prepared Statements require their input types to be known while most users write queries without specifying data types explicitly. The JDBC driver falls back to determining the untyped input as text instead of citext which forces a "text op text" comparison instead of a "citext op citext" one when the query is executed. The JDBC docs don't seem to cover this, which they should as it is their limitation, not ours (that I am aware of...), though I'm unsure exactly what the limitation stems from. David J.
