nyuuzyou/wikis huggingface dataset:
CNPJ

CNPJ validation implemented by Euler Taveira de Oliveira
in pure SQL.
--
-- Esta função retorna true se o CNPJ é válido e falso caso contrário
-- Ela verifica o tamanho e os dígitos verificadores
--
CREATE OR REPLACE FUNCTION verify_cnpj(text)
RETURNS BOOLEAN AS $$
-- se o tamanho for 14 prossiga com o cálculo
-- senão retorne falso
SELECT CASE WHEN length($1) = 14 THEN
(
 -- verifica se os dígitos coincidem com os especificados
 SELECT
 substr($1, 13, 1) = CAST(digit1 AS text) AND
 substr($1, 14, 1) = CAST(digit2 AS text)
 FROM
 (
 -- calcula o segundo dígito verificador (digit2)
 SELECT
 -- se o resultado do módulo for 0 ou 1 temos 0
 -- senão temos a subtração de 11 pelo resultado do módulo
 CASE res2
 WHEN 0 THEN 0
 WHEN 1 THEN 0
 ELSE 11 - res2
 END AS digit2,
 digit1
 FROM
 (
 -- soma da multiplicação dos primeiros 9 dígitos por 11, 10, ..., 4, 3
 -- obtemos o módulo da soma por 11
 SELECT MOD(SUM(res2) + digit1 * 2, 11) AS res2,
 digit1
 FROM
 (
 SELECT
 SUM(m * CAST(substr($1, 7 - m, 1) AS integer)) AS res2
 FROM
 (
 SELECT generate_series(6, 2, -1) AS m
 ) AS m11
 UNION ALL
 SELECT
 SUM(m * CAST(substr($1, 15 - m, 1) AS integer)) AS res2
 FROM
 (
 SELECT generate_series(9, 3, -1) AS m
 ) AS m12
 ) AS m2,
 (
 -- calcula o primeiro dígito verificador (digit1)
 SELECT
 -- se o resultado do módulo for 0 ou 1 temos 0
 -- senão temos a subtração de 11 pelo resultado do módulo
 CASE res1
 WHEN 0 THEN 0
 WHEN 1 THEN 0
 ELSE 11 - res1
 END AS digit1
 FROM
 (
 -- soma da multiplicação dos primeiros 12 dígitos por 5, 4, 3, 2, 9, 8, 7, ..., 3, 2
 -- obtemos o módulo da soma por 11
 SELECT MOD(SUM(res1), 11) AS res1
 FROM
 (
 SELECT
 SUM(n * CAST(substr($1, 6 - n, 1) AS integer)) AS res1
 FROM
 (
 SELECT generate_series(5, 2, -1) AS n
 ) AS m11
 UNION ALL
 SELECT
 SUM(n * CAST(substr($1, 14 - n, 1) AS integer)) AS res1
 FROM
 (
 SELECT generate_series(9, 2, -1) AS n
 ) AS m12
 ) AS m1
 ) AS sum1
 ) AS first_digit
 GROUP BY digit1
 ) AS sum2
 ) AS first_sec_digit
)
ELSE false END;
$$ LANGUAGE 'SQL'
IMMUTABLE STRICT;
COMMENT ON FUNCTION verify_cnpj(text) IS 'retorna verdadeiro se e, somente se, o CNPJ 
possui o tamanho correto (14 dígitos) e os dígitos calculados coincidem com os especificados';
Category:SQL
Category:Português
Cnpug

==用户会信息==
*关于用户会
*用户会组织架构
*用户会任务
==用户会活动==
*PostgreSQL2013中国用户大会
*PG2000 DBA免费培训活动
*其他过往活动
*各地分会
** 广州 联系人 Galy galylee@gmail.com
** 北京 联系人 禄永收 louis@easyea.com 
** 杭州 联系人 德哥 digoal@126.com
==沟通工具==
# 官方主页 
# bbs
# QQ群: 162729539
# 邮件列表
==资料库==
==项目一览==
# 文档翻译项目
# 内核代码解析项目
# 资料整理
Category:Users group Category:Chinese
Cn shanghai 11

=2011年11月27日Postgresql上海用户交流会=
#时 间:2011年11月27日 周日 1:30-5:30
#地 点: 南京东路步行街558号7楼咖啡厅（世纪广场）
#费 用: AA 饮料每人30元，晚饭每人30~50元
#报名方式: 27420716@qq.com(邮件内容注明 姓名、公司、联系方式、人数)
#联 系 人: 我行我素 QQ：27420716
#备 注： 活动不提供发票
#主 题: 上海及附近地区PostgreSQL用户互相认识交流的聚会, 彼此交流各自PG的使用情况, 促进PostgreSQL技术社区在中国地区的发展
#活动流程:
待定
时间 	编号 	主题 	演讲人 	演讲资料下载
2:00 -2:30	1 	签到 	无 	无
2:30 -3:00	2 	自我介绍，互相认识 	无 	无
3:00 -4:00	3 	社区情况简介、PostgreSQL的体系架构及内核导读(QQ视频远程) 	Galy 	无
4:00 -4:20	4 	使用Plproxy构建PG集群（视频） 	德哥 	无
4:20 -5:00	5 	自由交流 	全体 	无
6：00 - 	 	聚餐活动 	全体 	
*Galy
PostgreSQL 2011中国用户会全国大会召集人，中国用户会发起人；具有多年Postgres内核的开发经验。
* 德哥
斯凯网络DBA主管，多年数据库平台工作经验,熟悉Oracle,PostgreSQL,EnterpriseDB,GreenPlum,mongoDB等多种数据库平台,熟悉OS,存储等.负责斯凯网络数据库架构设计,性能调优与维护,存储系统设计与维护,OS维护等工作.
Category:Chinese
CodeCoverage

I have a patch that I will be submitting to add to the build system the capability of reporting on test code coverage metrics for the test suite. Actually it can show coverage for any application run against PostgreSQL. Download Image:Coverage.tar.gz to see an example report. Gunzip and un-tar the file and click on coverage/index.html. I had to delete most of the files to decrease the file size for upload, so only the links for access work.
gcov reports line, branch, and function coverage, but lcov only reports on line coverage. I've added a link to the html to the gcov output that shows summary statistics for each file for line, branch, and function calls.
The report gives a very clear and browseable view of what parts of the system might benefit from more extensive testing. It's obviously useful for planning future testing, but also can be used in conjunction with debugging to see what lines and functions are being exercised or missed by existing tests of the functionality under investigation. It could even be helpful to give a static view of lines hit by a bug test case in lieue of using a debugger. Also, when you're writing a unit test for new functionality, it would be good to check what you're actually hitting with the test.
It uses gcov together with gcc to generate the statistics, and the lcov suite to create the html report. Both of these would obviously have to be installed to get a coverage report, but this would be an optional feature of the build. It only works with gcc.
To generate coverage statistics, you run configure with --enable-coverage and after building and running tests, you do make coverage. The process generates data files in the same directories as source & object files and produces a coverage directory at the top level with the html files. I've also set it up so a tar file with the html is generated. That is what I've attached.
The current coverage for the master branch can be viewed at https://coverage.postgresql.org/. We turned off branch coverage because gcov's version seems uncapable of understanding out code completely; see https://www.postgresql.org/message-id/flat/30022.1520642188@sss.pgh.pa.us for background. We'll probably turn it on again once we have gcc-8.
More information on PostgreSQL test coverage at https://www.postgresql.org/docs/current/regress-coverage.html.
More information on gcov at http://gcc.gnu.org/onlinedocs/gcc/Gcov.html, lcov at http://ltp.sourceforge.net/documentation/how-to/ltp.php (coverage/lcov tabs).
Category:Development
CodeSprint2008

THIS IS A WIKI.
TO EDIT THIS PAGE:
Go to http://www.postgresql.org/community/signup and create an account. Then come back here, login (login link is on the upper right) and add your name to the Participants section.
==Code Sprint==
Join us on October 10, 1-5pm. 
We have a few hackers signed up to lead you through a code sprint on code from PostgreSQL and related projects. Come join us -- meet a few people, write some code and learn about the internals of PostgreSQL!
A code sprint is a structured programming session, designed to produce working code quickly! We will divide into teams, and work in pairs. Every 25 minutes or so, all groups will report back their progress. 
== How To Prepare ==
If you're bringing a laptop: load an SSH client, git, gcc, and the PostgreSQL source. If you need help with any of these, bring a sack lunch to the conference center at noon on October 10th for some help. 
Also see Andy Lester's excellent "Just Enough C For Open Source Projects": http://www.slideshare.net/petdance/just-enough-c-for-open-source-programmers
==Project Proposals==
Project: pg_top
Project Lead: Mark Wong
* Stored procedures for remote monitoring; Linux is done, help needed on FreeBSD, OpenBSD, OS X, Solaris, etc.
* Add screen for database level statistics.
* More ideas on pg_top TODO list.
Project: pg_ctl
Project Lead: Jeff Davis
* Fix a small bug in pg_ctl 
Project: Visual Planner
Project Lead: Tom Raney
Project: PgTAP
Project Lead: David Wheeler
Project: PostgreSQL TODO list item
Project Lead: Selena Deckelmann
==Participants==
Please put your name below if you plan to attend so that we can plan for the number of people who are attending. You do not need to choose a project at this time to participate in.
Jay Payne
Andrew Lardinois
Matt Smiley
Gabrielle Roth
Magnus Hagander
Jesse Young
==Long Description==
Curious about PostgreSQL internals and the
developers who make it happen? Wonder what it would be like to
contribute to an open source project? Want to get your hands dirty with
testing, documentation or the code?
Join us for 3 hours of hacking on PostgreSQL! Led by programming and
subject area experts, this session will pair you up with other
participants and current contributors to work on and contribute back to
the project.
Organized as a code sprint, you'll have a chance to hear from
developers about projects they're working on and then choose which
you'll be working on. Projects will range from application development
to documentation - in C, C++, PL/PgSQL and English.
No previous open source development experience is required to
participate. Flexibility and ability to work with others will be
necessary. If you'd like to work on code, familiarity with C will be
helpful -- see Andy Lester's excellent "Just Enough C For Open Source
Projects":
http://www.slideshare.net/petdance/just-enough-c-for-open-source-programmers
Projects will be available that do not involve C or coding. Technical
writers, graphic designers and project managers are welcome to attend!
PostgreSQL developers will be on-hand to give feedback and guidance.
You'll get a chance to work closely with them and other people in your
team.
Category:Advocacy
Color Palette

The main color is blue.
Blue 
*            dark blue : #0064a5
*            base blue : #336791
*            light blue : #008bb9
Grey
*            dark grey : #848484
*            base grey : #666666
*            light grey : #585858
Orange
*            dark orange : #cc3b03
*            base orange : #d24b03
*            light orange : #f26522
Category:Advocacy
Colors in SVG graphics

== Colors in SVG graphics for PostgreSQL's documentation ==
In the universe of 16 million colors there are some with an individual color name. In the past such color names were defined by various organisations or standards: X11, HTML, CSS, SVG, which leads to some confusion. SVG ended the attempt to define its own color names with version 1.1 (1.2 never gets an official standard), HTML with version 4.2.. HTML 5 as well as the current Candidate Recommendation for SVG 2.0 (04 October 2018) shift the responsibility of this issue to CSS .
We show some of these CSS color names, their values in hsl and rgb hex notation, both with opacity (alpha) of 1. If someone wants to change the opacity, he has different opportunities: SVG attribute opacity, hsla syntax, or rgba syntax, e.g.: rgba(255, 0, 0, 0.5). The use of an 8-digit-hex value is not recommended because it is not defined in CSS (and it seems to be implemented inconsistently: alpha-channel first or last?).
red 	 	hsl(0, 100%, 50%)#ff0000 	 	
yellow 	 	hsl(60, 100%, 50%)#ffff00 	 	
green / lime 	hsl(120, 100%, 25%)#008000	hsl(120, 100%, 50%)#00ff00	 	
aqua 	 	hsl(180, 100%, 50%)#00ffff	 	
navy / blue 	hsl(240, 100%, 25%)#000080	hsl(240, 100%, 50%)#0000ff	 	
black / gray / silver / white	hsl(0, 0%, 0%)#000000 	hsl(0, 0%, 50%)#808080 	hsl(0, 0%, 75%)#c0c0c0	hsl(0, 0%, 100%)#ffffff
For the use of colors within PG's SVGs we suggest to restrict them to a small number and - if you prefer color names instead of numeric values - the use of CSS names defined in the CSS standard.
Please select the colors of your graphics in the following order:
# Basic color names
# Extended color names
# HSL examples. HSL, RGB and Hex are equivalent notations to express color values (it's nothing but 'syntactical suggar' and there are many converters). For the generation of PDF documents we currently use fop in version 2.1. Unfortunatelly it does not support the HSL syntax. Therefor we are restricted to use RGB or Hex, though HSL is more intuitive.
# Any RGB or Hex value.
We prefer '50 shades of blue'.
Category:Documentation
Category:SVG
CommitFest

A CommitFest (CF) is a periodic break to PostgreSQL development that focuses on patch review and commit rather than new development. These are held so that all the work for a release gets relatively prompt review and feedback, and so that work for a release doesn't pile up until the end of the release cycle. During these periods contributors are asked to review and test the patches submitted by others. The hope is that this will also reduce the burden on those who do the final review and commit. The CF page is used to keep track of submitted patches and their status, to help manage the process.
When we're not trying to put together a major release CFs tend to run for one month each with a one month gap between them. Due to the process of getting a release out the door, though, there may be several months in a row without such a review cycle. After such a hiatus the first CF may be immediately preceded by a review-only phase before committers are able to participate at normal levels; such a phase may be called a ReviewFest (RF).
A CommitFest manager arranges for all the submitted patches to be reviewed. The peer review process often results in discussion on the pgsql-hackers list and/or requests for some sort of modification before commit. Most patches wind up getting committed, although some are returned with feedback (in hopes that the submitter will make some change and submit to a later cycle) or rejected (if they are determined by the community not to be useful changes). Once complete, a new Alpha release is produced for testing; after the final CommitFest for a release, a beta version is packaged.
The CommitFests are managed through our web application at commitfest application. Please submit/review/organise patches there.
* If you want to submit a new patch for review, please visit the Open CommitFest.
* If you want to help with the reviewing process for the commitfest that's currently taking place, please visit the In-progress CommitFest
If you want to contribute to the CommitFest application itself, that code is available in the CommitFest Repo
Category:CommitFest
CommitFest 2008-03

Category:PostgreSQL 8.4
= CommitFest - March 2008 =
This first CommitFest relied on Bruce's patch queue as its primary input:
* Patch Status Overview
* Bruce's Patch Queue
* Bruce's list of patches pending review
* Bruce's list of patches held for the next commitfest
== Pending patches ==
Below is the list of patches to be reviewed during the March Commitfest. If you have comments on them, please add them below each one, prepending each line with a colon (:).
If a patch must be punted to the next Commitfest, please remove it from here and add it there.
== Committed patches ==
If you commit a patch, please move it below this heading.
; Friendly help for psql
; Fix pg_dump dependency on postgres.h
; Truncate Triggers
; Better psql tab-completion support for schemas and tables
; suggested wording improvement in psql
; REFERENCED BY in psql
; Add size/acl information when listing databases
; Integer datetimes
; execute using
; Implemented current_query
; rewrite numeric division
; plpgsql, forc statement
== Reviewed patches ==
; SQL-language reference parameters by name v1.1
: review
; script binaries renaming
: We must conduct a poll on a wide audience, say pgsql-general. Zdenek?
: The poll seemed to agree that a "pgc" prefix command was the way to do it.
; Updated WITH clause patch (non-recursive)
; Fragments in tsearch2 headline
: Needs to be updated to apply against core tsearch instead of contrib. Teodor had other suggestions too.
; SQL/PSM
: This isn't maintainable unless it's refactored to eliminate code duplication with plpgsql.
; psql slash# command
: Author will revise based on discussion.
; Consistent \d commands in psql
: Discussion led to a redesign that now needs to be implemented.
; preread pages in bitmap index scan using posix_fadvise
: reviewed by: Simon, Heikki, Martijn
; Headers dependencies cleanup
: A more thorough investigation of layering of these header files has been requested.
; updated hash functions for postgresql v1
: The word-wide-hashing aspect of this has been cleaned up and applied; we still need to find out if we want to use the new mix() macro.
; Auto-explain patch
: Reviewed by Simon, needs more work to be ready
; Ordered Append WIP patch v1
: Reviewed here and here
; SET TRANSACTION conformance to SQL:2003
: Not needed, per discussion
; libpq type system
: latest patch
: start of April 2008 discussion
; Concurrent psql
: This is not proposed for application yet, but Greg needs feedback
: review of the UI
CommitFest 2008-03 Precursor

Subject 	Submitter 	Review Results	Blocker
Maintaining cluster order on insert 	Heikki Linnakangas	
 Tom Lane:This is superseded by a later submission.	
POSIX shared memory support 	Chris Marcellino 	
 Tom Lane:It's certainly far from clear what the point is...	
Stream bitmaps 	Heikki Linnakangas	
 Tom Lane:No patch here.	
Indexam interface proposal 	Heikki Linnakangas	
 Tom Lane:No patch here.	
Bitmapscan changes - Requesting further feedback	Heikki Linnakangas	
 Tom Lane:No patch here either.	
Auto Partitioning Patch - WIP version 1 	NikhilS 	 	
DSM, FSM, known-frozen pages 	ITAGAKI Takahiro 	 	
[HACKERS] CIC and deadlocks 	Pavan Deolasee 	 	
UPDATE using sub selects 	NikhilS 	 	
UPDATE using sub selects 	NikhilS 	 	
Better error message for select_common_type() 	Peter Eisentraut 	 	
row-level stats and last analyze time 	Neil Conway 	 	
plpgpsm 	Pavel Stehule 	
 Tom Lane:Wasn't this superseded by a recent submission?	
Updated bitmap index patch 	Gavin Sherry 	 	
Patch for pg_dump 	Dany DeBontridder 	
 Bruce Momjian:This is a TODO so we probably want this patch.	
Integer datetimes 	Neil Conway 	
 Bruce Momjian:I think we agreed to make this change for 8.4.
 Tom Lane: We agreed to switch configure's default for 8.4; I'm not convinced
 about anything longer-term than that. Neil, are you going to do the honors?	
Implemented current_query 	Tomas Doran 	 	
Concurrent psql patch 	Gregory Stark 	
 Bruce Momjian:This is not ready for application. Do we just add it to TODO?
 Tom Lane:Is there any useful review to be done during this commit fest? If
 not, it doesn't belong in this list.
 Tom Lane:Greg asked for review on the lists today, so I guess we do need to
 look at it ...	
Minor changes to Recovery related code 	Simon Riggs 	 	
WIP: script binaries renaming 	Zdenek Kotala 	
 Bruce Momjian:Ah, here is the patch that add pg_ to utility commands.	
WIP: rewrite numeric division 	Tom Lane 	
 Tom Lane:Not sure why we didn't just apply this in 8.3. The last couple of
 messages contemplate a feature addition (integer division operator) that's
 really a separate issue, but beyond that I'm not seeing any alternative
 choices.	
Category:Closed Commitfests
CommitFest 2008-07

Category:PostgreSQL 8.4
= CommitFest =
This is the page for CommitFest starting July 2008
 
 
 
 
== Round Robin Reviewers ==
Name 	Status 	Patch Count
Neil Conway 	Available	0
Jeff Davis 	Available	1
Pavan Deolasee 	Available	2
Andrew Dunstan 	Vacation 	0
Stephen Frost 	Available	2
Álvaro Herrera 	Available	0
Zdeněk Kotala 	Available	2
Thomas Lee 	Available	2
Abhijit Menon-Sen	Available	3
Bruce Momjian 	Available	2
Nikhil Sontakke 	Available	1
Greg Stark 	Available	1
Martin Zaun 	Available	1
CommitFest 2008-09

Category:PostgreSQL 8.4
__TOC__
This is the page for CommitFest starting 2008 September
== Pending patches ==
== Committed Patches ==
 
 
 
== Returned with Feedback ==
 
 
== Commuted to November Due to Prolonged Discussion ==
 
 
== Round Robin Reviewers ==
Name 	Status 	Reviewing	Completed
Brendan Jurd 	Available 	0 	2
Jaime Casanova 	Available 	1 	1
Stephen Frost 	Available 	1 	0
Jeff Davis 	Available 	1 	0
Greg Stark 	Available 	1 	0
Martin Zaun 	Only 9/8 to 9/15	1 	0
Álvaro Herrera 	Not Available 	0 	0
Zdeněk Kotala 	Not Available 	1 	0
Thomas Lee 	Not Available 	0 	0
Abhijit Menon-Sen	Available 	2 	0
Nikhil Sontakke 	Not Available 	0 	0
Alex Hunsaker 	Available 	1 	0
Markus Wanner 	Cherry-picking 	0 	3
Ibrar Ahmed 	Available 	0 	1
D'Arcy Cain 	Available 	1 	0
Abbas Butt 	Available 	1 	0
Kenneth Marshall 	Available 	1 	0
CommitFest 2008-11

Category:PostgreSQL 8.4
__TOC__
This is the page for the CommitFest starting 2008 November.
Managers for this CommitFest are Josh Berkus (josh-at-agliodbs-com) and Dave Page (dpage-at-pgadmin-org).
== Committed patches ==
 
 
 
== Returned with Feedback ==
 
 
== Rejected Patches ==
 
 
== Round Robin Reviewers ==
Name 	Status 	Reviewing	Completed
Brendan Jurd 	Available 	0 	4
Jaime Casanova 	Available 	1 	1
Stephen Frost 	Available 11/15	0 	0
Jeff Davis 	Available 	0 	5
Greg Stark 	Unknown 	1 	0
Abhijit Menon-Sen	Unknown 	0 	0
Alex Hunsaker 	Available 	0 	6
Markus Wanner 	Cherry-picking 	1 	1
Ibrar Ahmed 	Available 	1 	2
D'Arcy Cain 	Unknown 	0 	0
Kenneth Marshall 	Available 	1 	1
Robert Haas 	Available 	0 	11
Matthew Wetmore 	Out-of-contact 	0 	0
Gianni Colli 	Available 	1 	0
"Unicron" 	Available 	1 	4
Pavan Deolasee 	Partly-Done 	0 	1
CommitFest 2009-First Archive

__TOC__
This is the page for the first 8.5 CommitFest (starting July 15, 2009).
== Pending patches ==
|-
| colspan="4" |
=== Security ===
 
|-
| colspan="4" |
=== Replication ===
|-
| colspan="4" |
=== Performance ===
|-
| colspan="4" |
=== Contrib modules ===
|-
| colspan="4" |
=== Clients ===
|-
| colspan="4" |
=== SQL language features ===
|-
| colspan="4" |
=== EXPLAIN ===
|-
| colspan="4" |
=== Instrumentation ===
|-
| colspan="4" |
=== Error Reporting ===
|-
| colspan="4" |
=== Miscellaneous ===
== Committed patches ==
== Returned with Feedback ==
Community Generated Articles, Guides, and Documentation

=Major article and documentation topic subsections=
* Detailed installation guides
* Converting from other Databases to PostgreSQL
* Database Administration and Maintenance
* Development with PostgreSQL
* Performance Case Study
* PostgreSQL Performance Optimization
* Frequently Asked Questions
* Replication, Clustering, and Connection Pooling
=Community Generated Articles=
== Introductory ==
* Introduction to PostgreSQL Rules - Making entries which can't be altered by Justin Clift (2001-07-20)
* A flash tutorial on Sequences by Justin Clift
* A flash tutorial on Referential Integrity by Justin Clift
== Other Applications ==
* PostgreSQL ecosystem - a directory of software and cloud services that support or use PostgreSQL
* PostgreSQL Clients
* Community Guide to PostgreSQL GUI Tools
* Design Tools - GUI tools for ERD schema design
* Qmail using PostgreSQL user authentication by Michael Devogelaere
* HOWTO: PostgreSQL and Crystal Reports by Mike Godshall (2004-03-24)
* Using PostgreSQL for a Domino 6 RDBMS Backend (pdf) by Keith Perry
* Using Echelon SQL Scripter with PostgreSQL by Branden Williams and Matt Springfield
* PostgreSQL derived databases
* Using Open Office Base 2.3.1 with PostgreSQL Postgres OnLine Journal (January/February 2008)
* Using OOo Base to connect to PostgreSQL - OpenOffice.org Wiki
== PostgreSQL Usage ==
* PostgreSQL Change data capture (CDC) + golang sample code.
* A Brief Real-world Trigger Example by Richard Huxton
* Retrieving Database meta-data from the Information Schema by Lorenzo Alberton (2006-05-02)
* PostgreSQL 101 by Shridhar Daithankar (2006-05-01)
* FAQ: Working with Dates and Times in PostgreSQL by Josh Berkus (2001-08-25)
* How to avoid overlapping intervals with PostgreSQL by Matteo Nastasi (2001-07-16)
* COPY by Jeff Eckermann (2001-09-17), rewritten (2008-03-02) Evan Carroll
* PostgreSQL 9.0 Cheat Sheet by Postgres OnLine (September/October 2010)
* PostgreSQL 8.3 TSearch Full-Text Search Cheat Sheet by Postgres OnLine (May/June 2008)
* PostGIS related study guides Regina Obe and Leo Hsu
* Don't Do This
== Troubleshooting ==
* Operations cheat sheet
* Generating a stack trace of a PostgreSQL backend
= Deprecated articles =
These are articles that are not really applicable to current versions of PostgreSQL, but are kept here for those still running those old versions:
* Information on the 8.1.4/8.0.8/etc. Security Release
* Tips for upgrading PostgreSQL from 6.5.3 to 7.0.3 by Mark Stosberg
* Overview of new features in PostgreSQL 7.4 by Josh Berkus and Joe Conway (2004-02)
* Replication HOWTO: Setting up RServ with PostgreSQL 7.0.3 by S.Gopi (2001-09-13)
* Usogres Replication Test report by Dobrica Pavlinusic (2002-04-22)
* HOWTO : Full Text Indexing with PostgreSQL using contrib/fulltextindex by Christopher Kings-Lynne (2002-04-07)
* PostgreSQL for Enterprise Business Applications by Ron Chmara (2002-01-29)
!