causing crash - Search results in mailing lists
Mailing lists >> pgsql-docs >> Thread
2020-04-13 21:11:30 | Ambiguos statement in wal-async-commit page (PG Doc comments form)
crashed, it didn't actually perform the action of dropping table nor was it logged in WAL, then how it would cause
Mailing lists >> pgsql-docs >> Thread >> Search in thread (2)
2018-11-29 04:35:17 | Updating the intro for packages - improve usability, reduce new user confusion (Craig Ringer)
cause: The PostgreSQL manual, including the intro/tutorial, is written with the assumption you installed from source and are using pg_ctl, etc directly. Very few of our users do this. The reality is that most
Mailing lists >> pgsql-docs >> Thread
2016-11-23 20:13:13 | Re: Missing important information in backup.sgml (Gunnar \"Nick\" Bluth)
caused by your DB server vanishing (burning down, exploding, melting, ...), f) a complete _loss_ of the DC (atomar strike, plane crash
Mailing lists >> pgsql-docs >> Thread
2016-06-13 18:59:37 | Re: Regarding Overcommit (Kevin Grittner)
causes a crash and restart of all connections without necessarily giving any useful clues as to the cause
Mailing lists >> pgsql-docs >> Thread
2010-05-07 21:13:50 | Re: [HACKERS] no universally correct setting for fsync (Tom Lane)
crash/, perhaps. The wording you have suggests that a forced Postgres stoppage produces a problem, which it doesn't. It takes a failure at the OS level or below to cause
Mailing lists >> pgsql-docs >> Thread
2006-10-24 00:39:55 | Replication documentation addition (Bruce Momjian)
crash. This shared hardware functionality is common in network storage devices. This allows sychronous, full replication. Warm Standby Using Point-In-Time Recovery ----------------------------------------- A warm standby server (add doc xref) can be kept current
Mailing lists >> pgsql-docs >> Thread
2001-01-23 12:54:43 | [HACKERS] WAL documentation (Oliver Elphick)
crash during writing could result in: 1. index tuples pointing to non-existent table rows; 2. index tuples lost in split operations; 3. totally corrupted table or index page content, because of partially written data