Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 0f85db9

Browse filesBrowse files
docs: use consistent markup for PostgreSQL
"PostgreSQL" should use <productname> markup consistenktly, so that if we do apply styling on it it will be consistently applied. Fix by renaming the one exception to the rule. Discussion: https://postgr.es/m/F2EF5217-27A3-4962-9AE5-2E6C2CB3D0FF@yesql.se
1 parent 106f26a commit 0f85db9
Copy full SHA for 0f85db9

File tree

1 file changed

+1
-1
lines changed
Filter options

1 file changed

+1
-1
lines changed

‎doc/src/sgml/datatype.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/datatype.sgml
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2672,7 +2672,7 @@ TIMESTAMP WITH TIME ZONE '2004-10-19 10:23:54+02'
26722672
To complicate matters, some jurisdictions have used the same timezone
26732673
abbreviation to mean different UTC offsets at different times; for
26742674
example, in Moscow <literal>MSK</literal> has meant UTC+3 in some years and
2675-
UTC+4 in others. <application>PostgreSQL</application> interprets such
2675+
UTC+4 in others. <productname>PostgreSQL</productname> interprets such
26762676
abbreviations according to whatever they meant (or had most recently
26772677
meant) on the specified date; but, as with the <literal>EST</literal> example
26782678
above, this is not necessarily the same as local civil time on that date.

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.