nyuuzyou/wikis huggingface dataset:
Zsasha's Treasures

Zsasha's Treasures are items in Drawn to Life: The Next Chapter (Wii) that can be found in every world except Jangala. They are one of three optional collectibles in the game, and one of the five optional challenges. As their name implies, the challenges are presented to the Hero by Zsasha.
== Appearance ==
The treasures, while all having different names, all share the same appearance. They all look like Zsasha's backpack, which in turn takes the appearance of a purple knapsack with a golden buckle. It has two purple straps and a brown belt that would wrap around the wearer's waist.
== Levels==
(Note: The name of the treasure will be listed under the icon and name of each level.)
Shadow LabyrinthBubblegum Ring
Shadow PalaceLava Lamp
Crystal CavernsHideout Sign
FrozeniniCrystal Comb
Floating MeadowsTennis Raquet
Balancing Rock GardenPropeller Helmet
== Trivia ==
* During the Hero's first interaction with Zsasha in Rapoville, he mentions that if the Hero collects the treasures, they might be rewarded. However, no such reward exists.
** However, this reward may be the Sword that Zsasha gives the Hero after unknown circumstances are met.
* According to a Game Design Document shared by Ken Capelli, each of the six treasures were planned to be found in different gates.
** The Bubblegum Ring would have been found in Jangala, the Lava Lamp would have been found in Shadow City, an Ice Flower would have been found in Icy Wastes instead of the Crystal Comb, the Tennis Racquet would have been found in Eastern Winds, the Hideout Sign would have been found in the cut Water World, and the Propeller Helmet would have been found in the cut Space World.
== Media==
ComingSoon.png
__NOTOC__
Category:Objects
Category:Drawn to Life: The Next Chapter (Wii)
Category:Shadow City
Category:Icy Wastes
Category:Eastern Winds
Category:Levels in Drawn to Life: The Next Chapter (Wii)
Category:Collectibles
Main Page

__NOTOC__
= Welcome to the PostgreSQL Wiki! =
This wiki contains user documentation, how-tos, and tips 'n' tricks related to PostgreSQL. It also serves as a collaboration area for PostgreSQL contributors.
== User Documentation ==
* Frequently Asked Questions
==== Community Generated Articles, Guides, and Documentation ====
* General articles and guides
* PostgreSQL Tutorials
* PostgreSQL Related Code Snippets
* Detailed installation guides
* Converting from other Databases to PostgreSQL
* Comparison with other Database systems
* Database Administration and Maintenance
* Development with PostgreSQL
* PostgreSQL Performance Optimization
* PostgreSQL Related Slides and Presentations
==== Documentation on the main site ====
* PostgreSQL Manuals 
* PostgreSQL Books
== Alternate Languages ==
The following pages contain user documentation in languages other than English.
* deutsch
* español 
* français
* עברית
* 日本語
* português
* русский
* 中文
* 中文（繁體
== Contributor Information ==
* You can find many PostgreSQL users and developers chatting in #postgresql on Libera. A list of IRC nick names with their respective real world names can be found here.
* Upcoming Events
* Development information
* Advocacy
== User Accounts ==
* All activity on this site should follow the PostgreSQL Project Policies. 
* In order to edit or create documents on the site, you will need a PostgreSQL community account. This is the same account used when submitting news or events on www.postgresql.org.
NOTE: due to recent spam activity "editor" privileges are granted manually for the time being. If you just created a new community account or if your current account used to have "editor" privileges ask on either the PostgreSQL -www Mailinglist or the PostgreSQL IRC Channel (direct your request to 'pginfra', multiple individuals in the channel highlight on that string) for help. Please include your community account name in those requests.
20110905pg upgrade fix

= Critical Fix for pg_upgrade/pg_migrator Users 2011-09-05: Details =
The following are details of the pg_upgrade and (formerly) pg_migrator fix published to the announce email list on 2011-09-05 and to be fixed in Postgres 8.4.9, 9.0.5, and the 9.1 final releases. (It is not fixed in 9.1rc1 and earlier 9.1 releases.)
== What can you tell me about this bug? ==
It has been discovered that the bug fix outlined in 20110408pg_upgrade_fix did not fix problems for people upgrading from PostgreSQL 8.3. The same diagnosis and solutions outlined in 20110408pg_upgrade_fix apply for this bug (those who upgrade from PostgreSQL 8.3).
== How can I get a fix? ==
You can wait for official releases or pull the current git tree for the desired branch. Most users who are upgrading from 8.3 need to build their own version of PostgreSQL anyway to adjust for the datetime storage format change in PostgreSQL 8.4 from float to 64-bit integer.
== Who discovered this bug? ==
This problem was reported by depesz and diagnosed by Bruce Momjian.
Category:Release notes
2011cpug

1.邮件报名
 报名邮箱：cpug2011@gmail.com.
 主要信息包括：姓名，单位，职务，座机，手机，邮件，邮寄地址，邮编。
 注：请准确填写手机、常用邮件等信息。
2.电话确认
 我们根据收到报名信息后，将给报名者进行电话确认，并说明、落实、查看付款情况等。
 注：一旦正式报名开始，就要着手电话确认、汇款付款、门票等事务的操作。
3.汇款付费
 根据自己所选择的门票类型，并按本文提供的付款方式，支付相关票款。
 3.1 门票类型
 企业票:以公司企业名义参加，如针对公司企业的DBA. 个人票:个人，主要面对数据库爱好者或开源软件爱好者，如学生。
 3.2 汇款帐号
 特别说明：一旦您购买大会门票，恕不退票。本次大会主要采取银行汇款、转账方式收取付款。
 1) 向指定银行卡号汇款，请注明 你的姓名 以及注明“PG2011全国大会”字样。
 2) 大会汇款账号：银行电汇、网银汇款、企业转账均可汇款（汇款查询时间：实时）
 汇款确认短信电话：*****(姓名)
 户名：*****
 帐号： ***** 
 开户行：****
 注：如需发票，请电话沟通，开据发票名目：信息服务费(或广告费)。
4.获取门票
 收到付款后，会务组将与你再次电话确认，并根据提供的邮寄地址寄送大会的门票（正式纸质门票）。
 届时，参会签到时，凭门票即可换取大会证件(胸卡)、餐券、大会资料等。两天开会期间，不用再签到，仅需凭借大会证件(胸牌)参会（可将大会证件转送他人）。
Category:Users group Category:Chinese
2013UnconfFakingIt

We discussed creating random data to fill a database that is to be used as an example.
Some useful queries for generating random data:
select random() from generate_series(1,3); -- Generates random numbers
select (array[...])[random() * nelems + 1]; -- Selects random elements from an array
select now() - ‘1 year ago’::interval * random() -- Gives you random dates over the last year
select uuid_generate_v4(); -- Generates a uuid
To affect a random subset of your rows, update where random() < 0.3 for example
We then decided it would be useful to have a sample database available for public consumption. There is already one example database available at github.com/pgexperts/librec, but we wanted one that implemented a lot more PostgreSQL features and had lots of random data in it. We could make one that would be used to store data about PGCon.
Demo database needs:
hstore
full text search
range type
auditing tables
foreign keys
views
roles
spatial data
functional indexes
array
constraint partitions
listen/notify
The start of this project is available on github at:
https://github.com/pvh/postgresql-sample-database
Lastly, we also discussed the desire for an extension for plotting and graphing data visually called e.g. pg_graph. One example function it might provide is something to plot x,y points using ascii art.
2013UnconfFutureOfJSON

Future of JSON
What people are using JSON for, binary representation, etc.
Peter talked about MoSQL & PL/v8. People don't know JSON from 9.3 yet.
What we need:
* indexing
Dunstan published pgjpath on bitbucket, which implements jpath via PL/v8.
Need to think about what operations need to be supported via index. Like can jpath be indexable. Like trigram? We probably don't need find similarity.
Range queries? We would need to agree on types. 
* Numeric numbers (arbitrary length)
* strings, 
* booleans, 
* and NULL. 
Do we want to support timestamps? Mongo does this in BSON, we don't know now. Maybe later.
Pluck a fragment out of an array.
Josh wants to update one value at a time in place instead of rewriting the entire blob. Mentioned doing this by hacking TOAST, but it would break transactions. Both ondisk storage and in-memory representation are issues. Maybe manip palloc. Oracle's nested tables also mentioned.
Distinguishing between binary representation and text representation. pg_upgrade would have to scan the whole table. We'd need a different page number. Users would need to run the check option first. Bruce doesn't want pgupgrade to modify the old cluster. We'd need a separate cleanup program. 
There was a discussion about deprecating the code which upgrades hstore1 (the 8.3 version) to hstore2 (the 9.0 version). Teodor doesn't want to support this anymore. Bruce pointed out that we can't deal with that in pgupgrade. 
More discussion about JSON upgradability.
We need some addtional functions for the new JSON:
* akeys
* slices
etc. David Wheeler has list.
So we need to support all of these using JSON.
Alvaro asked for the ability to do multi-update. That is update all items which match a path.
2013UnconfReplicationWishlist

Minutes: Replication Features Wishlist
- Replication features to replicate individual columns. It was mentioned that Bucardo does something for column replication
- In systems like Slony, duplicating the names of tables that get replicated to multiple nodes, setting it up can be a pain, so ways to rename tables
- Discussion to replicate to a totally different database. Example mongo->mysql etal are available. Postgres->Redis? There's a logical difference between multiple databases and even something completely different
- Instantaneous switching of roles from master to a slave. Single command to switch the roles. Christopher Browne mentioned that "slony move" does something of this sort already.
- Sharding based replication logic: In EC2 kinds of cases the replication set to send to nodes should be based on some partitioning logic. But in this case the hard part is to handle re-allocation when a row moves from a partition to another. Chris opined that sharding if it should be done should be based on "dates". It's more natural and non-changing.
- Event triggers could already be useful in handling deletion of tables that are Slony replicated. You could disallow that or if "CASCADE", think of doing it on the replica setup as well.
- DDLs pushing through to replicas is a pain point. So DDL and corresponding locking needs to be handled appropriately. Discussion specific to Slony and locking pains when trying to push DDL changes. Maybe a wrapper can be written which can identify which objects are involved and CHECK on all replicas if they are available. So a probable solution is out there.
- Wonder if we can convert Slony, Londiste, Bucardo into custom background workers. We need to restart PG to do something like this though.
 
- Discussion about if some features can be put into the core to handle monitoring requests from HA agents
- Slony still useful for upgrades and partial replication cases. Streaming replication is not going to handle those cases
2024.pgconf.dev Patch Review Workshop

Conference: https://2024.pgconf.dev/
Session: https://www.pgevents.ca/events/pgconfdev2024/schedule/session/40-patch-review-workshop-registration-required/
Please do not add patches to the lists below. Instead, contact Robert and Andres and send them your suggestions. Thanks.
== Suggested Patches for More Experienced Reviewers ==
* Extract numeric field in JSONB more effectively by Andy Fan
* Show WAL stats on pg_stat_io by Nazir Bilal Yavuz (reviewed by group of Bharath, Ilya, Andrey)
* Use read streams in CREATE DATABASE command when the strategy is wal_log by Nazir Bilal Yavuz
* Support prepared statement invalidation when result or argument types change by Jelte Fennema-Nio
* Virtual generated columns by Peter Eisentraut
* Switching XLog source from archive to streaming when primary available by Bharath Rupireddy
* Add LSN <-> time conversion facility by Melanie Plageman (reviewed by group of Bharath, Ilya, Andrey)
* Amcheck verification of GiST and GIN by Andrey Borodin
* apply_scanjoin_target_to_paths and partitionwise join by Ashutosh Bapat
* Recheck foreign key if a referenced collation was nondeterministic by Paul Jungwirth
* Fix rare recovery shutdown hang by Thomas Munro
* SetLatches by Thomas Munro
* Add pg_wait_for_lockers() function by Will Mortensen
== Suggested Patches for Less Experienced Reviewers ==
* Adding comments to help understand psql hidden queries by Greg Sabino Mullane
* teach pg_combinebackup to detect deleted files where possible by Robert Haas
* SupportRequestRows support function for generate_series_timestamptz by David Rowley
* Add memory context type to pg_backend_memory_contexts view by David Rowley (David C)
* Run deferred triggers in the correct security context by Laurenz Albe
* Should consider materializing the cheapest inner path in consider_parallel_nestloop() by Tender Wang (to review by Paul, Tomasz, Yuki)
* Reuse child_relids in try_partitionwise_join by Ashutosh Bapat (David C)
* Reduce the log spam by excluding certain SQLSTATEs by Laurenz Albe (Bilal, Melih, Trevor)
* pg_parse_json: don't leak token copies on failure by Jacob Champion
* Flush disk write caches by default on macOS and Windows by Thomas Munro
* Restrict EXPLAIN (ANALYZE) for RLS and security_barrier views by Laurenz Albe
* Support for named parsed statement in psql by Anthonin Bonnefoy
* functions to compute size of schemas/AMs by Justin Pryzby (David, Stefan, Joseph)
64bit Windows port

Note: 64bit Windows port was introduced in PostgreSQL 9.0.
== 64bit Windows Port ==
This page is for collating info and working up a TODO list for producing an eventual Win64 port of PostgreSQL. As there is generally no reason to run with shared_buffers > 256 - 512MB on Windows, because increases beyond that stop being effective, there isn't a great deal of incentive to put in the effort required for the 64 bit port. There are a few reasons though:
* 64 bit applications may require a 64 bit libpq.dll.
* Some end users/customers like the warm fuzzy feeling they get from running 64 bit binaries on their 64 bit machines.
* Users may want to use custom C functions that make use of external 64 bit libraries.
* Users may want to use procedural languages that use 64 bit interpreters.
* Sooner or (probably) later Microsoft will likely deprecate their 32 bit tool chain.
* Magnus blogged why a win64 port is not too urgent: http://swik.net/PostgreSQL/Planet+Postgresql/Magnus+Hagander:+PostgreSQL+vs+64-bit+windows
The following subsections list the issues that need to be resolved in broad categories.
=== Code changes ===
* Build system
* Datatypes used in the backend (*much* more detail is required here folks!)
=== Support libraries ===
We'll need 64 bit builds of these support libraries to avoid turning off expected features.
* MIT Kerberos - the current expectation is that this will be dropped entirely in favour of SSPI
* OpenSSL - Unofficial 64 bit build available from http://www.deanlee.cn/programming/openssl-for-windows/
* Gettext - http://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/
* Iconv - http://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/, or see http://monetdb.cwi.nl/projects/monetdb/MonetDB/Documentation/Windows-Installation.html for manual compilation info. Totally unofficial build at blender.org: https://svn.blender.org/svnroot/bf-blender/trunk/lib/win64/iconv/
* libxml2 - see http://monetdb.cwi.nl/projects/monetdb/MonetDB/Documentation/Windows-Installation.html for manual compilation info.
* libxslt
* zlib - http://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/, or see http://monetdb.cwi.nl/projects/monetdb/MonetDB/Documentation/Windows-Installation.html for manual compilation info. Totally unofficial build at blender.org: https://svn.blender.org/svnroot/bf-blender/trunk/lib/win64/zlib/
* libxml2 and libxslt are available within the PHP-Windows-builds at http://pecl2.php.net/downloads/php-windows-builds/php-libs/
Hint: other people also look for those libraries, connecting http://wiki.wireshark.org/Development/Win64
=== Procedural languages ===
* Perl - Activestate package: http://www.activestate.com/activeperl/downloads/
* Python - official builds at http://www.python.org/download/releases/2.5.4/, Activestate 2.5 build at http://www.activestate.com/activepython/downloads/
* TCL - Tcl 8.4.9 should support AMD64 out-of-the-box says Jeff Hobbs, The Tcl Guy http://coding.derkeiler.com/Archive/Tcl/comp.lang.tcl/2005-05/msg00866.html
Category:Windows
Category:PostgreSQL 9.0
84WebTasks

== Website Preparation ==
The following changes all need to be prepared so that they can go out in one commit at the appropriate time. Please put your name next to items which you can claim, and mark them when done.
* Home Page
** Call Box should say "8.4 Release" and have appropriate links -- Dave STAGED
** Latest Releases should rotate to 8.4 and 7.4 should drop off -- Dave STAGED
* News
**Write Internal announcement for News Item and Submit -- Josh
**Check News Item
*developers/beta:
**Needs to change to "Beta is over" page. -- Dave STAGED
*about/press:
**Gather all presskits and translations -- Josh DONE
**Need someone to review all of the new materials -- Dave FINAL CHECK DONE, STAGED
***Correct presskits -- Josh DONE
**Create TOC for about/press -- Dave STAGED
*about
**Feature Matrix: "8.4dev" should change to "8.4" -- Dave STAGED
*Documentation
**"8.4 beta" should change to "8.4" -- Dave STAGED
**"What's New" link should point to 8.4 release notes -- Dave STAGED
*External
**Submit Release to PRWire -- Josh
== Scheduled Deployments ==
Here's the things which need to be done, and the times they need to be done. Given issues in the past, we should have a responsible and a backup person for each task. The schedule below assumes a July 1st release. Please add tasks as appropriate.
UTC Time 	EDT Time 	Task 	Person 	Backup 	Done?
6/29 21:00	6/28 17:00	Move FTP files to main FTP 	Marc 	Josh 	DONE
7/1 11:00 	6/30 07:00	Load new docs into website database 	Dave 	 	DONE
7/1 11:15 	6/30 07:15	Merge changes into website 	Dave 	 	DONE
7/1 11:15 	6/30 07:15	Approve news item 	Dave 	 	DONE
7/1 11:30 	6/30 07:30	Schedule website rebuild, inc. docs 	Dave 	 	DONE
7/1 14:00 	6/30 10:00	Send out pgsql-announce 	Josh 	Bruce 	
7/1 19:00 	6/30 15:00	Update Freshmeat, SourceForge, etc. 	Jonathan Fuerth	Josh & Devrim	
7/1 19:00 	6/30 15:00	Submit to SlashdotServerSide,StumbledUpon	Josh 	 	
Category:PostgreSQL 8.4
85AlphaFeatures

This page contains a list of features, for publication for each alpha release.
== Alpha1 ==
=== SQL ===
* DROP COLUMN and DROP CONSTRAINT now support an IF EXISTS clause so that you can avoid errors when running repeatable scripts.
* UNIQUE constraints can now be DEFERRABLE
=== Performance ===
* GEQO generic algorithm query plans, for very complex queries, can be made repeatable by setting a geqo_seed. This will help with debugging bad plans generated by GEQO.
=== Stored Procedures / Functions ===
=== Administration and Monitoring ===
* You may now display the SQLSTATE error code as part of the log_line_prefix in your log by using the %e switch.
=== Tools ===
* pg_standby no longer links to a specific libpq version, preventing unnecessary incompatibility issues.
* pgbench is now multi-threaded, allowing it to use multiple CPU's for its client connections.
=== psql ===
* The \d+ describe table shortcut now shows the child tables which inherit from the specified table.
* The \di index describe command now shows the index method.
=== Other ===
* We have change the names of some internal functions to remove conflicts with C++ reserved words. This will make it easier to plug-in C++ code to the PostgreSQL codebase.
Category:PostgreSQL 9.0
9.0beta3announcement

The third beta release for PostgreSQL version 9.0 is now available. This beta contains numerous fixes and several changes since Beta2, including a final clean-up of Streaming Replication and Hot Standby. Please download, install, and test it so that we can move towards final release of 9.0.
Some significant changes have been introduced in beta3 which will require some applications to be re-tested with 9.0. These include:
* Fixes for hot standby: 
** close walwriter filehandles faster
** fsync on master before sending WAL
** improved handling of archive cleanup (archive_cleanup_command and pg_archivecleanup contrib module)
** better handling of WAL record corruption
** change of standby delay settings and timing
* Fix for array handling in plpython
* Many dblink fixes
* TCP keepalive support in libpq
* Fix for checkSeek() behavior on old platforms (was causing pg_dump to occasionally fail)
Note that, due to a system catalog change, an initdb and database reload will be required for upgrading from 9.0Beta1. We encourage users to use this opportunity to test pg_upgrade for the upgrade from Beta2 or an earlier version of 9.0. Please report your results.
If you are able to help with beta testing, please see the Beta testing page.
Betas are not stable and should never be used in production; they are for testing only. Additional beta releases, or a release candidate, will be available for testing in a few weeks.
Source code, as well as binary installers for many platforms, is available from the PostgreSQL Web Site:
* Source
* One-Click Installer, including Win64 binaries
* Binaries for other platforms
* Release Notes
* Participating in Testing
Category:PostgreSQL 9.0
9.0beta4announcement

The fourth beta release for PostgreSQL version 9.0 is now available. This beta contains numerous fixes and a few changes since beta3. As this is likely to be the last beta release, please download, install, and test it so that we can move toward final release of 9.0.
Beta4 contains primarily bug-fixes in response to user testing reports since Beta3. The one significant user-facing change is to report \timing information even when psql is being run in "quiet" mode. Fixes include:
* Report disk space error properly and do not load .psqlrc when using pg_upgrade;
* Allow full SSL certificate verification when host and hostaddr are both specified, backpatched to 8.4;
* Fix for pg_dump's handling of SQL/MED objects;
* Bugfix and performance improvement for scans of lossy GIN index pointers;
* Fix for possible page corruption in ALTER TABLE .. SET TABLESPACE;
* Properly replay CREATE TABLESPACE during crash recovery;
* Cleanup subtransactions in FOR loops, and avoid deep recursion when assigning XIDs to multiple levels of subtransactions, both backpatched to 8.0.
Unlike previous betas, there has been no system catalog change since Beta3, so an initdb should not be required to upgrade test databases from Beta3. Upgrading test databases from earlier versions or betas will require an initdb, however, so we urge users to take the opportunity to test upgrading their database using 9.0's pg_upgrade and report the results.
If you are able to help with beta testing, please see the Beta testing page.
Betas are not stable and should never be used in production; they are for testing only. A release candidate will be available for testing soon.
Source code, as well as binary installers for many platforms, is available from the PostgreSQL Web Site:
* Source
* One-Click Installer, including Win64 binaries
* Binaries for other platforms
* Release Notes
* Participating in Testing
Category:PostgreSQL 9.0