nyuuzyou/wikis huggingface dataset:
Pgcon2014unconferenceExtensionWishlist

===PostreSQL Extension System Wishlist===
The following items were brought up as useful improvements to the PostgreSQL extension code:
# Planner hooks for extensions
# A way to add trigger-extension dependencies, e.g. ALTER EXTENSION ... ADD TRIGGER ...
# A way to specify how extension-owned objects' ownership changes (or doesn't) when the table to which they're attached changes ownership
# Whitelist listing extensions which non-superusers may install at their discretion
# Multiple versions of an extension installed simultaneously
# Ability to grant permission to install an extension instead of permissions flowing through to the actions taken by the extension code.
# Object metadata (key/value pairs on db objects)
# Some way to remove code duplication between full and upgrade sql scripts e.g. by changing the install process to use the latest full sql and then apply incremental sql scripts to get to a particular version. 
# Better automation of upgrading & testing
# Inline extensions allowing additional files to be installed without server access
# Make check w/o install
# Global extension dir/listing (not sure what this means now...)
# Build farm that could e.g. check installability of all modules on pgxn
# Package auto build (not sure what this means now...)
# A list of extensions "blessed" by the PostgreSQL community as stable, well-supported, etc. and some way to determine if an extension makes it onto this list.
Category:Unconference
Pgcon2014unconferenceVODKAandJSQuery

Leaders: Alexander Korotkov, Teodor Sigaev
== Updating item pointers in an index file ==
(Korotkov) Vodka maintains two index files, one for keys and one for heap item
pointers (postings). Each index file can be, in effect, managed by a
different access method. This is a generalization of GIN, which uses btree
(albeit its own btree code, not src/backend/access/nbtree) for both keys and
postings. The keys index file has item pointers that refer to the postings
index file. When the postings file's access method needs to move an index
item, it must arrange to update any item pointer in the keys file. To that
end, proposing a new "amupdateiptr" access method function. Calls to that
function, when necessary, will arrive right after an amgettuple call.
(Heikki Linnakangas) Vodka separates one GIN idea (extract keys from input
values) from an independent GIN idea (store heap item pointers in some way
other than flatly, one per key). The latter idea is helpful by itself when
you have many duplicate keys. Instead of storing the key many times, store it
once and point to a posting tree/list. (Korotkov) Indeed, the motivating
application for Vodka was use of a GiST-managed R-tree for postings.
(Sigaev) When the access method of one index file calls amupdateiptr for
another index file, the first access method is holding a buffer lock across
that call. It would be better to avoid that, but how?
== Tracking the two files of a Vodka index ==
(Korotkov) How should we track the existence/identity of the two index files?
(Linnakangas) Let the access method of the keys file be in control. If the
keys are in a btree, btree is responsible for tracking any posting structure.
(Tom Lane) Posting tree representations are not a datatype-independence
problem; the data is always item pointers. There's a fixed number of possible
storage strategies, so allowing arbitrary access methods and operator classes
for postings is needlessly general. Put a version number on disk in case we
think of additional methods later, though. (Oleg Bartunov) We chose that
approach for easy experimentation with different posting representations.
== Getting OID of opclass/operator ==
(Korotkov) Vodka operator classes declare a "config" function that returns an
opclass OID and an operator OID. Implementing the config function is awkward,
because non-core objects do not have stable OIDs. It's not so simple as doing
a name lookup like a reg* cast would do. Might need a new syscache.
== JSQuery ==
(Sigaev) Proposing query language for searching in jsonb; see slides. An
implementation of the proposal exists, but statistics and planner support
aren't done. (Andrew Dunstan, unknown speakers) Why is the query language
itself not in json? Why not use an already-standardized language, such as
JPath? MongoDB has a query language. (Dunstan, Bartunov) MongoDB query
language is too verbose. (unknown speaker) People migrating from MongoDB
would value compatibility. (Dunstan) Especially if the idea is to use this
for something resembling schema validation, it would be better to follow an
established standard.
Category:Unconference
PgCon 2016 Developer Unconference

An Unconference-style multi-track (three tracks are currently planned) event for active PostgreSQL developers will be held from the afternoon of Wednesday 17 May, 2016 at the University of Ottawa, as part of PGCon 2016. This Unconference will be focused on technical PostgreSQL development discussions ranging from Clustering and replication to the infrastructure which runs postgresql.org.
Note: See the schedule at the bottom of this page.
== Unconference schedule by Time and Room ==
{| border="1" cellpadding="4" cellspacing="0"
!Time
!DMS1160
!DMS1110
!DMS1120
|- style="background-color:lightgray;"
|Wed 11:15-12:15
|Partitioning
|Database schema validating tools
|Ephemeral relations
|- style="background-color:lightgray;"
|Wed 13:15-14:15
|Logical replication in core
|Wait events monitoring
|Page compression
|- style="background-color:lightgray;"
|Wed 14:30-15:30
|IO improvements + buffer cache scaling 
|Transaction manager + multimaster
|How to get started reviewing
|- style="background-color:lightgray;"
|Wed 16:00-17:00
|Executor performance
|Parallel index building 
|Async execution
Category:Unconference
Pgcon2016userunconference

= pgCon 2016 User Unconference Day =
The PostgreSQL Community is having our third User Unconference Day at pgCon 2016 in Ottawa! This event, extends pgCon and gives us additional opportunities to share, collaborate, and discuss about PostgreSQL development, hacking, usage, and community.
For more about unconference days and why we're doing this, see the Unconference Day FAQ.
If you are interested in holding a session, or you want someone else to do a session on a particular topic on the Unconference day, please add your proposal to "session ideas" below.
== Basic Information ==
pgCon User Unconference Day
Saturday, May 21st
10am to 5:30pm
Rooms: TBD
Lunch with Pizza Provided
Sponsored by: Salesforce.com
== User vs. Developer Unconference ==
This year, for the first time, we will be having a User Unconference and a Developer Unconference. The Developer Unconference will be on Wednesday, and its topics will be restricted to ones around contributing to PostgreSQL and major features currently under development. 
This page is for the User Unconference, which is on Saturday, and can include topics from any attendee at pgCon. While some of the topics will be about current PostgreSQL development, we also encourage you to bring late-release PostgreSQL related technology which emerged too late for the pgCon CFP. Or even discussion sessions about the community and other issues.
== Unconference Schedule ==
Important: if you are planning to propose as session, you need to be at the unconference at 10am sharp!
Time 	DMS 1160 	DMS 1110 	DMS 1130
10am 	Session Pitches and Scheduling - Coffee and snacks	 	
10:45AM 	PostgreSQL ProjectCode of Conductdiscussion 	 	
12:00 Noon	Lunch! 	 	
1:00PM 	Multi-Master Demo 	User Complaints 	Postgres on FreeBSD
2:15PM 	Bug Tracker Discussion 	Replaying SQL 	PGCAC Annual MeetingPostgreSQL Trademark Q&A
3:30PM 	PgInfra & Web Team 	Figures & Pics in Docs	Running Postgres in Containers
== Session Ideas ==
Please post your ideas for Unconference Sessions below. This could include either sessions you want to lead, or sessions you wish someone else would lead. Sessions which are proposed in advance and receive upvotes here on the wiki will be given priority when it comes time to pitch them.
Please use this template:
 === My Session Idea Name Here ===
 
 Proposed By: 
 
 Session Leader: 
 
 Description: 
 
 People who want to attend this session please put your names below:
 
*
=== Pictures/Figures/Diagrams in documentation ===
 
Proposed By: Ilya Kosmodemiansky
 
Session Leader: Ilya Kosmodemiansky
 
Description: 
There are no pictures in PostgreSQL documentation, which looks a bit ridiculous today. Recently the topic was raised again by Tatsuo Ishii and discussion demonstrates that it is quite important. I suggest to discuss, what kind of pictures we would like to have (user feedback needed) and possible technical implementation. 
 
People who want to attend this session please put your names below:
 
*
Category:PGCon2016
Category:Unconference
PgCon 2017 Developer Unconference

== Unconference schedule by Time and Room ==
{| border="1" cellpadding="4" cellspacing="0"
!Time
!DMS1160
!DMS1110
!DMS1120
|- style="background-color:lightgray;"
|Tue 11:15-12:15
|Flipping the executor upside down + JIT compilation
|Upgrading Postgres without downtime
|
|- style="background-color:lightgray;"
|Tue 12:15-13:15
|Lunch
|
|
|- style="background-color:lightgray;"
|Tue 13:15-14:30
|Pluggable storage
|PGAudit
|
|- style="background-color:lightgray;"
|Tue 14:30-16:00
|Partitioning - what next
|indirect indexes
|
|- style="background-color:lightgray;"
|Tue 16:00-17:00
|64-bit XID
|Planner stuff
|Statement level rollback
Category:Unconference
PgCon 2018 Developer Unconference

== Unconference schedule by Time and Room ==
{| border="1" cellpadding="4" cellspacing="0"
!Time
!DMS1160
!DMS1110
!DMS1120
|- style="background-color:lightgray;"
|Tue 11:15-12:15
|Scale out architecture and development / Global snapshots
|JIT Compilation
|Get Rid of SLRU Move To Buffer Cache
|- style="background-color:lightgray;"
|Tue 12:15-13:15
|Lunch
|
|
|- style="background-color:lightgray;"
|Tue 13:15-14:15
|Pluggable Table Access Methods
|Monitoring - Tools, Metrics, Integration, Dashboards
|Extensions, versioning, hooks, etc
|- style="background-color:lightgray;"
|Tue 14:15-14:30
|Coffee Break
|
|
|- style="background-color:lightgray;"
|Tue 14:30-15:30
|HA - architecture and components, multi-master
|Undo logs
|Query optimizer for partitioned tables
|- style="background-color:lightgray;"
|Tue 15:30-16:00
|Break
|
|
|- style="background-color:lightgray;"
|Tue 16:00-17:00
|Redesigning the query executor (room 1140)
|Decouple connection from backend / multi-process and multi-thread
|Table level TDE
Category:Unconference
PgCon 2020 Developer Meeting

NOTE: This meeting is not happening since PGCon 2020 was moved online.
----
A meeting of the interested PostgreSQL developers is being planned for Tuesday 26 May, 2020 at the University of Ottawa, prior to pgCon 2020. In order to keep the numbers manageable, this meeting is by invitation only.
Any questions regarding the invitations to this event should be directed to the team of individuals tasked with coming up with the list of people to invite:
* Andres Freund
* Stephen Frost
* Dave Page
The invitation list for the meeting has changed this year to include representatives from various project sub-teams, for example, packagers, the release team, Code of Conduct committee and more.
An Unconference will be held on Friday for in-depth discussion of technical topics.
This is a PostgreSQL Community event.
== Meeting Goals ==
* Define the schedule for the 14.0 release cycle
* Address any proposed timing, policy, or procedure issues
* Receive updates from project sub-teams on their activities and discuss any resulting issues or concerns.
* Address any proposed Wicked problems
== Time & Location ==
The meeting will (probably) be:
* 9:00AM to 3PM
* DMS 3105 - Desmarais Hall, 55 Laurier Avenue East
* University of Ottawa.
Lunch will be served during the meeting.
== RSVPs ==
The following people have RSVPed to the meeting (in alphabetical order, by surname). Note that we can accommodate a maximum of 30!
# Andres Freund
# Stephen Frost
# Dave Page
The following people will not be in Ottawa, and do not plan to attend:
== Agenda Items ==
* 14.0 release and commitfest schedule (Dave)
* Please add suggestions for agenda items here. (with your name)
==Agenda==
Time 	Item 	Presenter
09:00am - 09:10am	Welcome and introductions	Dave Page
10:30am - 11:00am	Coffee break 	All
12:00pm 	Lunch 	All
2:50pm - 3:00pm 	Any other business 	Dave Page
Note: This timetable is a rough guide only. Items will start as soon as the previous discussion is complete (breaks will not move materially however). Any remaining time before lunch may be used for Commitfest item triage or other activities.
Category:Developer Meeting
PgCon 2020 Developer Unconference/Building Benchmarks

Note: To be saved in wiki.postgresql.org after session.
Talking points:
 	1. Competitive Benchmarking
 		2. Metrics
 			3. Performance
 				4. TPS/TPM: Transaction Rate OLTP oriented
 				4. Query Execution time: e.g. BI oriented - how fast does a reporting query run
 				4. Load time: BI oriented
 				4. Refresh time: BI oriented
 			3. Cost - is this practical with open source?
 				4. Professional services
 				4. Hardware - maybe just detailed hardware configuration
 			3. Other metrics
 		2. How to enforce fairness?
 			3. Licensing
 				4. GPL: recommended
 				4. Artistic License: not OSI approved
 			3. Neutral site for publications
 			3. Other aspects/topics
 	1. Open Source Benchmarking Kit
 		2. Considerations
 			3. Create or adapt a project that people can agree to work together on
 				4. Licensing
 				4. Language
 				4. Postgres specific or inclusive to other open source projects?
 			3. Start with a simple workload
 				4. Easy to run
 				4. Easy to develop
 		2. Designs
 			3. BI
 				4. Schema Design & Data Generation
 				4. Queries
 			3. OLTP
 				4. Schema Design & Data Generation
 				4. Transaction Definitions
 				4. Workload Profile
 				4. Transaction manager: build vs use existing
 				4. Driver: how to build
 			3. Others?
 	1. Stay in touch?
 		2. Mailing list
Category:Unconference
PGCon 2021 Fun With WAL

Notes from PGCon 2021 Unconference session "Fun with WAL"
=== Fun with WAL ===
- There are some cool things we could with the WAL
- Faster archive recovery
- Lazy or partial restore, only replay WAL when it's needed
- Push API to replace archive_command
==== Zenith architecture ====
 WAL
 PostgreSQL ----------------> Page Server
 
 GetPage@LSN
 ---------------->
 <----------------
- PostgreSQL streams the WAL to the page server using Streaming Replication.
- Page Server applies the WAL
- No (relation) data is stored in the PostgreSQL data directory
- smgr / md layer has been replaced with calls into the Page Server
==== Faster archive recovery ====
Perform WAL redo in two phases:
1. Scan the wal, make note of which record applies to which page.
2. Whenever you see a full-page image for a block, all the previous records for same
block can be immediately thrown away. (This can be made much more effective by
writing an extra full-page image e.g. every 1000 updates on the same page.)
3. After the first phase, wal redo can be performed separately for each relation or block.
that's a better, more sequential I/O pattern.
Parallel WAL redo:
After the WAL has been split per relation, each relation can be restored in parallel
Instant Recovery:
You can actually start up the cluster, before WAL redo has finished. Whenever a page
is accessed, replay all the WAL applicable to that record on demand.
http://wwwlgis.informatik.uni-kl.de/cms/fileadmin/publications/2017/PhD_Thesis_Caetano_Sauer.pdf
==== Lazy Restore ====
Restoring cluster from base backup requires copying all the data from the backup,
and replaying all the WAL.
- If we split the WAL in the backup, per relation, it would be possible to restore only what's needed.
- with Lazy Restore, non-relational stuff, like clog, would be restored as usual.
- When a relation is accessed for the first time, it's fetched from the backup, on demand, and the WAL applicable to that relation is replayed
==== Problems / annoyances ====
Some things are currently not included in WAL records:
- cmin/cmax
- speculative insertion tokens
These are not needed for crash recovery, but are needed by the primary server
With some WAL records, it's complicated to decipher which blocks are affected.
For example:
- The visibility map and FSM updates are implicit with heap WAL records
- XLOG_SMGR_TRUNCATE truncates the heap, the FSM and VM in one operation
- pg_rewind suffers from these too
==== Synchronous replication woes ====
If a WAL record cannot be streamed out, we still write it to local disk.
There was discussion on this last year in PGCon...
==== Push API for WAL ====
To replace archive_command
==== Corrupt WAL and security ====
- We could use with more sanity checks in WAL redo routines
- Can we make a guarantee that the WAL redo routines can tolerate any corrupt WAL without crashing? (Currently we can't.)
Category:Unconference
Pgconchina2011Cond

== PostgreSQL 2011全国用户大会即将举行 ==
经过紧张的筹备，PostgreSQL 2011全国用户大会即将举行，敬请关注。
本次会议是有国内PostgreSQL的志愿者发起的，旨在促进PostgreSQL在中国发展的非营利性的会议，全国的PostgreSQL相关的企业及技术人员可以每年定期交流PostgreSQL的企业应用、架构设计、运维管理、应用开发方面的经验，促进PostgreSQL在中国的发展。 
下面是会议的详细信息：
1. 大会信息
 日 期: 2011年7月15日-16日 
 大 会 地 址： 广州市黄埔大道西601号暨南大学第二文科楼516多功能会议厅 
 交 通： 地铁(3号线岗顶D出口)， 公交(师大暨大站，国防大厦站)
 内 容: PostgreSQL的企业应用、架构设计、运维管理、应用开发 
 大会网页 ： http://wiki.postgresql.org/wiki/Pgconchina2011
 咨询邮箱： cpug2011@gmail.com
2. 大会纪念品
 本次大会推出大会T恤，不参加的朋友也可购买
 http://wiki.postgresql.org/wiki/Pgconchina2011Tshirt
3. 大会议程
首日 First Day: 7月15日 July 15, 2011 
9:00 开始报到及领取资料 
 
July 15, 9:30am PostgreSQL简介 An Introduction to PostgreSQL 周正中 Digoal 
July 15, 10:30am PostgreSQL原理简介 PostgreSQL Internal 李元佳 Galy Lee 
July 15, 11:30am 动态数据库模型Socrates及其PostgreSQL实现 An dynamic database model and its implementation in PostgreSQL 刘鑫 March Liu 
July 15, 12:00pm 午餐Lunch 
July 15, 14:00 GREENPLUM CHORUS: Cloud Computing for Data Warehousing and Analytics 庄富任 Fujen Chuang(EMC) 
July 15, 15:00 SQL聚类扩展语句Cluster-by：PostgreSQL实现, Implementing Cluster-by in PostgreSQL 孙鹏 Sun Peng 
July 15, 15:40 SQL语言解析器的实现--为BDB添加SQL支持 SQL Query Processing Implementation 黄坚 Huang Jian 
4:30pm - 5:00pm 照集体相 （take photo） 大会全体人员all attendees 
第二日 Second Day: 7月16日 July 16, 2011 （英语演讲有现场翻译） 
 
9:00 - 09：10 15 Minutes 简介和欢迎 Welcome and Introductions 李元佳 Galy Lee 
09:10 - 10：00 1 Hours 主题演讲（英语）Keynote: 在pgpool-II中使用PostgreSQL的流复制功能 石井达夫 Tatsuo Ishii 
10:00 - 11：00 1 Hours 主题演讲（英语）Keynote David Fetter 
11:00 - 12：00 1 Hours PostgreSQL开源数据库应用实践(The practice for using postgresql in enterprise) 周正中 Digoal Zhou 
12:00 - 14：00 午餐 Lunch 
14:00 - 15：00 1 Hours PostgreSQL 的集群 PostgreSQL HA and clustering architecture 萧少聪 Scott Siu 
15:00 - 16：00 1 Hours PostgreSQL社区及在中国的发展 PostgreSQL Community and its development in China 李元佳 Galy Lee 
16:00 - 17:00 1 Hours 小组讨论: 如何促进中国的PG社区发展, 用户期待PG还需要哪些改进 Panel Discussion 众专家及与会者 
18:00 - 22:00 晚宴 Party （暂定珠江夜游及在船上自助餐自由交流） 由于成本问题 仅限已交钱个人或企业名义报名用户
Category:Chinese
Category:PostgreSQL Events
Pgconchina2011Tshirt

针对今年7月于广州举办2011年PG用户大会，现推出大会纪念T恤订购，欢迎大家订购。
http://www.yincl.cn/TShirt/
*尺寸
尺寸 	肩宽 	胸围 	袖长 	衣长 	身高(cm)
XXL 	52 	116 	22.5	75 	180~185
XL 	50 	114 	22 	72 	175~180
L 	48 	109 	21.5	70 	170~175
M 	46.5	103 	21 	68 	165~170
S 	42 	100 	20 	65 	160~165
*联系方法
 请发送邮件到大会报名邮箱：
 发送邮箱Email： CPUG2011@gmail.com 
 邮件标题Title： 2011年PG用户全国大会纪念T恤订购 + 姓名
 邮件内容Subject：
 姓名 Name：
 手机 Mobile： 注：便以短信联系
 尺寸 Size： 注：根据以上尺寸选择合适的Size
 邮件 Email： 注：请填写常用邮件
 邮寄地址、邮编Address： (重要)
*价格
39元/件(不含运费)
*图片
Category:Chinese
Category:PostgreSQL Events
PGConf.Asia 2016

= PostgreSQL Conference Asia 2016 =
== Website ==
* http://www.pgconf.asia/en/2016/
== Talks ==
* DAY1-A1 : What’s New in 9.6, by PostgreSQL contributor, Masahiko Sawada
* DAY1-A2 : Parallel Query In PostgreSQL!, Amit Kapila
* DAY1-A3 : Using PostgreSQL in Tantan　– From 0 to 350bn rows in 2 years, Victor Blomqvist
* DAY1-A4 : Case Study: Application of PostgreSQL　to the large social infrastructure – Intorduction, Kunio Tanji / Ayumi Ishii
* DAY1-A4 : Case Study: Application of PostgreSQL to the large social infrastructure – First half, Kunio Tanji
* DAY1-A4 : Case Study: Application of PostgreSQL to the large social infrastructure – Second half, Ayumi Ishii
* DAY1-B1 : Hitachi’s efforts to apply PostgreSQL to mission critical systems, Tsuyoshi Inagaki
* DAY1-B2 : Why PostgreSQL? Story of Fujitsu’s footprints with PostgreSQL, Yamamoto Akinori / Higuchi Daisuke
* DAY1-B3 : PL/CUDA – The fusion of HPC grade computing power with in-database analytics, Kaigai Kohei
* DAY1-B4 : Migrations to PostgreSQL, Venkata B N
* DAY2-A1 : YeSQL: Battling the NoSQL Hype Cycle with Postgres, Bruce Momjian
* DAY2-A2 : PostgreSQL Backups the modern way, Magnus Hagander
* DAY2-A3 : Performance Improvements in PostgreSQL 9.5, 9.6 and beyond, Tomas Vondra
* DAY2-A4 : PGroonga – Make PostgreSQL fast full text search platform for all languages!, Kouhei Sutou
* DAY2-A5 : Evolution of pgAdmin: pgAdmin4, Dave Page
* DAY2-B1 : PGXZ：Large-Scale Distributed DBMS (Application to Mobile Payment System), Xu Zhongqing
* DAY2-B2 : Beyond EXPLAIN: Query Optimization Behind the Scenes, Yuto Hayamizu
* DAY2-B3 : Pgpool-II: Past, Present and Future, Tatsuo Ishii / Yugo Nagata
* DAY2-B4 : Logical Replication, Sharding & Multimaster Clusters, Simon Riggs
* DAY2-B5 : What are the similarities and differences of using PostgreSQL between Japan and Europe?, Yoko Takase
* DAY2-K2 : A History of the PostgreSQL Project, Peter van Hardenberg
* DAY2-K2 : PostgreSQL Story in China, in Alibaba Cloud(Aliyun), Scott Siu
== Tutorials ==
* SELECT & performance, Kosuke KIDA
* SQL drill, Taketomo SONE
* Introduction to data analysis with PostgreSQL, Masanori OYAMA
Category:PostgreSQL Events
Pgconfchina2012-admin

PG 2012 大会项目管理
==大会演讲主题（孙鹏、德哥）==
*会议主题
*参会嘉宾资料
*大会会议资料
==大会报名及宣传（荣茂）==
*大会报名网站准备
*大会宣传工作
*大会报名统计
*大会收费及发票(Galy)
*大会资料准备
==大会会场会务（永收、少聪）==
*会场确定
*大会横幅，拉纸
*大会主持(Galy, 德哥，孙鹏，Francs)
*会场协助管理(每个会场两人)
*报到及接待工作
*大会纪念品(T恤)
*大会胸卡
*大会资料手册
*大会摄影
*书籍赞助协调(图灵，华章)
==PG ACE颁奖活动(德哥)==
*颁奖名单
*颁奖奖品
*颁奖流程
==大会嘉宾接待（Galy）==
*嘉宾接送
*大会晚宴
*嘉宾旅游
==大会项目跟踪协调(泥鳅)==
Category:Chinese
Category:PostgreSQL Events
Pgconf cn2013 coreteam

=今后的工作重点和计划=
*宣传推广工作
*网站建设工作
*盈利模式的探索
*组织工作的建设
*文档翻译
=工作分工=
* 组织机构改革(李元佳)
用户会会目前面临的工作日益复杂，需要进行相应的改革以满足相应的需求。用户会依然坚持非盈利为核心的准则，以促进Postgres在中国的推广和普及为使命，用户会会的主要管理人员均为兼职及志愿者。未来的用户会管理机构分两层，首先是有30个人组成的用户会会委员会，委员会为用户会的代表组织，需要五人以上的委员提名，或者是常委提名，需要过半数的常委通过即可成为委员，委员任期一年。其次，委员会投票选出9人常委，候选人由委员提名，得票前九为常委，常委任期两年，同时选出用户会会会长，投票需要至少2/3委员参与，用户会会长连任不超过两届。每年所有用户会成员，对常委进行投票，选出工作突出的，进行奖励。每年的用户会全国大会期间，举行委员会的工作会议，商量明年工作。用户会的核心事务由常委投票进行决策。
*1组：宣传推广组：目的主要是推广Postgres，提高其知名度(萧少聪，李元佳)
**组织2014年全国大会
**和高校建立合作形式，推广PG
**与培训机构建立合作关系
**网站门户、杂志、软文的
**其他相关展会的参加
*2组：网站组：目的是建立用户会的官方网站，作为中文Postgre信息的主要集散地(周到京，阿弟)
**负责网站的改版设计工作
**负责网站的服务器管理
**负责网站的内容更新
**负责网站的搜索引擎优化工作
网站目前的突出问题是没有真正起到门户的作用。用户会的官方网页需要支撑用户会作为一个正式组织的运作，包括用户会的信息、新闻、会员管理、相关资料、活动组织等方面的功能支持，同时还需要改进相应的用户体验，成为Postgres新闻最权威的发布渠道。我们目前已经成了的网站组，有兴趣的朋友可以加入，QQ群是：297962353
*3组：文档翻译：完成官方文档的本地化工作(泥鳅，刘媛媛)
**负责翻译团队的搭建
**负责新文档的翻译，发布
**完成9.3文档的翻译
翻译工作是国内中文社区比较重要的一个问题，没有文档，会使得PG的使用面临比较大的障碍。目前我们只有8.2的文档已经翻译成功，但是后续的翻译做的不是很成功，其中一个很重要的原因是我们没有一个很好的平台和机制，同时也没有一个稳定的团队。今年的会把这些基本的体制建立起来，争取在明年把9.3文档中文化这个事情完成。同时我们也可以探索一下，是否能够每年的最新版本收费之类的模式，能够吸引更多人翻译更高质量的文档。我们目前已经成了的翻译组，有兴趣的朋友可以加入，QQ群是：309292849
*4组：活动组织：各地用户会的活动发起，组织，协调，全国大会的组织(德哥、逯永收)
**负责全国用户会本地组织的建设（广州、深圳、北京、杭州、西安、上海成立分会）
**组织协调本地活动（广州、深圳、北京、杭州、西安、上海各地）
**负责用户会会的会员管理，会务工作(成立会员入会的登记系统)
我们目前的活动组织还存在一些问题，用户会目前的会员管理没有真正建立起来，包括会员的注册，定期的会刊，还有活动的参会这些都没有真正做起来，所以今年我们趁用户会网站改版，把这部分功能也加进来，把会员的信息的管起来。另外，我们各地的用户会目前的组织还不是特别完善，各地没有形成一个活跃和自运转的一个组织，今年我们重点建设广州(含深圳)、北京、杭州、西安、上海这几个地方的用户会，本地成立当地的团队，用户会可以提供相应的资源支持本地的活动。今年争取每个地方至少举行一次活动，我们做年度计划的时候把全年的计划都计划好。我们目前各地比较缺乏积极的人员，尤其是西安和上海，目前还没有正式的组织，如果有兴趣的人员可以联系德哥。
*5组：用户会杂志会刊(孙鹏、君羊、Jack)
**负责会刊的内容编辑、发行
**11月开始每月发行一期杂志
作为用户会会对外的正式官方期刊，对外发放信息。
*6组：商业发展组(Francs)
**纪念品销售
**书籍销售
用户会目前缺乏相应的经济来源，以支持用户会会活动的开展，包括会议场地，纪念品，还有服务器等，现在希望探索一下相应的商业发展模式。所有的收入透明管理，相应经费的使用需要活动用户会过半常委的同意才能使用。
*7组：开发社区组(有理想的猪)
**开发的基础设施的构建
**特性的协调组织(插件、中文的全文检索、其他内核特性)