85 Commits (bf523f97ca8f0286c2e027caa85edcdb8558eda2)

Author	SHA1	Message	Date
Bruce Momjian	51c3727903	Move client encoding libpq function docs into libpq doc section, and ... just reference them from the localization doc section. Backpatch to 8.3.X.	18 years ago
Tom Lane	70b9b9b788	Change initdb and CREATE DATABASE to actively reject attempts to create ... databases with encodings that are incompatible with the server's LC_CTYPE locale, when we can determine that (which we can on most modern platforms, I believe). C/POSIX locale is compatible with all encodings, of course, so there is still some usefulness to CREATE DATABASE's ENCODING option, but this will insulate us against all sorts of recurring complaints caused by mismatched settings. I moved initdb's existing LC_CTYPE-to-encoding mapping knowledge into a new src/port/ file so it could be shared by CREATE DATABASE.	19 years ago
Tatsuo Ishii	6041b92238	Make JOHAB client only encoding per discussions in pgsql-hackers ... "Server-side support of all encodings" around 2007/3/26. initdb required.	19 years ago
Tatsuo Ishii	75c6519ff6	Add new encoding EUC_JIS_2004 and SHIFT_JIS_2004, ... along with new conversions among EUC_JIS_2004, SHIFT_JIS_2004 and UTF-8. catalog version has been bump up.	19 years ago
Bruce Momjian	a134ee3379	Update documentation on may/can/might: ... Standard English uses "may", "can", and "might" in different ways: may - permission, "You may borrow my rake." can - ability, "I can lift that log." might - possibility, "It might rain today." Unfortunately, in conversational English, their use is often mixed, as in, "You may use this variable to do X", when in fact, "can" is a better choice. Similarly, "It may crash" is better stated, "It might crash". Also update two error messages mentioned in the documenation to match.	19 years ago
Bruce Momjian	5b7be582e2	Update the UTF-8 RFC reference. RFC 2044 was obsoleted by RFC 2279, ... which was obsoleted by RFC 3629. Michael Fuhr	19 years ago
Bruce Momjian	32cebaecff	Remove emacs info from footer of SGML files.	20 years ago
Tom Lane	0fd087af83	Fix table title.	20 years ago
Tom Lane	b8cd6b4f25	Make it clearer that not every Postgres character set can be used as a ... server-side character set.	20 years ago
Peter Eisentraut	1b658473ea	Add support for Windows codepages 1253, 1254, 1255, and 1257 and clean ... up a bunch of the support utilities. In src/backend/utils/mb/Unicode remove nearly duplicate copies of the UCS_to_XXX perl script and replace with one version to handle all generic files. Update the Makefile so that it knows about all the map files. This produces a slight difference in some of the map files, using a uniform naming convention and not mapping the null character. In src/backend/utils/mb/conversion_procs create a master utf8<->win codepage function like the ISO 8859 versions instead of having a separate handler for each conversion. There is an externally visible change in the name of the win1258 to utf8 conversion. According to the documentation notes, it was named incorrectly and this changes it to a standard name. Running the Unicode mapping perl scripts has shown some additional mapping changes in koi8r and iso8859-7.	20 years ago
Peter Eisentraut	39dfbe5791	Spellchecking run, final cleanups	20 years ago
Tom Lane	a9980ec37b	Describe the behavior of the SQL_ASCII encoding more accurately.	20 years ago
Tom Lane	6f7fc0bade	Cause initdb to create a third standard database "postgres", which ... unlike template0 and template1 does not have any special status in terms of backend functionality. However, all external utilities such as createuser and createdb now connect to "postgres" instead of template1, and the documentation is changed to encourage people to use "postgres" instead of template1 as a play area. This should fix some longstanding gotchas involving unexpected propagation of database objects by createdb (when you used template1 without understanding the implications), as well as ameliorating the problem that CREATE DATABASE is unhappy if anyone else is connected to template1. Patch by Dave Page, minor editing by Tom Lane. All per recent pghackers discussions.	21 years ago
Tom Lane	85eee28cec	Minor improvements to locale documentation.	21 years ago
Neil Conway	957f51ea6b	Add a reference to the documentation on alternate index operator classes in ... the locale docs. Patch from Chris KL, editorialization by Neil Conway.	21 years ago
Bruce Momjian	17c8276d24	Clean up win1252 documentation. Mention how we determine the number of ... bytes/character for each encoding.	21 years ago
Bruce Momjian	e7fb9f18bf	Add support for Win1252 encoding. ... Roland Volkmann	21 years ago
Neil Conway	9abced035d	Fix mistakes in SGML markup. From David Fetter.	21 years ago
Bruce Momjian	d1022ce3a1	Document client-only encodings.	21 years ago
Bruce Momjian	a03bb609b3	Finalize character set documentation changes.	21 years ago
Bruce Momjian	cbc100af66	Increment all major version numbers in 8.0.X to force recompile of ... client aplications so 7.4.X releases can be installed on the same machine as 8.0.X.	21 years ago
Bruce Momjian	0edc2f14e0	More ordering adjustments.	21 years ago
Bruce Momjian	c151e6374c	Fix markup.	21 years ago
Bruce Momjian	119807e397	More markup changes.	21 years ago
Bruce Momjian	1c0aeec65b	More cleanups.	21 years ago
Bruce Momjian	cbe4b4163e	More improvements.	21 years ago
Bruce Momjian	a717ab6fa6	More additions to the table.	21 years ago
Bruce Momjian	1fa8445233	Keep changing the markup until I like it. :-)	21 years ago
Bruce Momjian	382f24b187	More table markup improvements.	21 years ago
Bruce Momjian	7b7abb7ccb	More table markup fixes.	21 years ago
Bruce Momjian	6109a1ce18	Rework "aliases" column for encodings.	21 years ago
Bruce Momjian	074ba31e41	Fix markup typo.	21 years ago
Bruce Momjian	f949baf9a2	Add missing conversion documentation for certain encodings.	21 years ago
Bruce Momjian	e42e3b6c56	Reorder documented encodings to be alphabetical. ... Remove warning about pre-7.2 LATIN5 usage.	21 years ago
Bruce Momjian	ee1bd33dd0	Document aliases for our supported encodings. ... Add a few encodings that were not documented.	21 years ago
Bruce Momjian	852ef58da9	Documention all our supported encodings.	21 years ago
Bruce Momjian	e3d7de6b99	Rename canonical encodings, per Peter: ... UNICODE => UTF8 ALT => WIN866 WIN => WIN1251 TCVN => WIN1258 The old codes continue to work.	21 years ago
Bruce Momjian	246be304a5	Add mention of performance impact on LIKE of non-C locales.	21 years ago
Tom Lane	008e9e452f	More minor updates and copy-editing.	21 years ago
Neil Conway	ec7a6bd9a2	Replace "--" and "---" with "&mdash;" as appropriate, for better-looking ... output.	21 years ago
Peter Eisentraut	152a101f2b	Allow WIN1250 as server encoding.	22 years ago
Neil Conway	fd4f3b3b62	Improve the locale and character set docs, add some <xref>s pointing ... to the character set docs where appropriate, and improve the postmaster reference page. Character set cross-refs suggested by Gavin Kistner.	22 years ago
Neil Conway	80ec228389	Refer to GUC variables using <xref> tags rather than <varname> tags, ... where appropriate. Add "id" and "xreflabel" tags to the descriptions of the GUC variables to facilitate this. Also make a few minor docs cleanups.	22 years ago
Tom Lane	5e54515167	Recommend SHOW, instead of pg_controldata, for checking LC_COLLATE and ... LC_CTYPE settings of a database.	22 years ago
PostgreSQL Daemon	969685ad44	$Header: -> $PostgreSQL Changes ...	22 years ago
Peter Eisentraut	1d27de4cf4	Random copy-editing.	22 years ago
Bruce Momjian	188eda0df2	Consistenly lowercase GUC variable names, in docs and error messages.	23 years ago
Peter Eisentraut	c326d8f4f2	Add/edit index entries.	23 years ago
Tom Lane	4c3c8c048d	Remove --enable-recode feature, since it's been broken by IPv6 changes, ... and seems to have too few users to justify maintaining.	23 years ago
Peter Eisentraut	2c0556068f	Indexing support for pattern matching operations via separate operator ... class when lc_collate is not C.	23 years ago