postgresql   32467

« earlier    

The Internals of PostgreSQL for database administrators and system developers
In this document, the internals of PostgreSQL for database administrators and system developers are described.
postgresql  postgres  database  book  online  administration  tutorial  reference 
19 hours ago by vicchow
postgres-migrations - npm
Stack Overflow style database migrations for PostgreSQL
postgresql  migrations  sql  data  npm  nodejsinteractive 
20 hours ago by program247365
PostgreSQL: Re: Methods to quiesce PostgreSQL DB without configuring log archival
>> If archive_mode is not configured, and i use snapshot solution for backup of
>> the server, how can i ensure data consistency? Is there a way to quiesce all
>> the connections to DB?
>
> If your snapshot solution is atomic, then you are *probably* okay. I would
> do a few restores to test, but atomic snapshots give you a point in time and
> should be consistent.



You should be OK *if all files in the backup are part of a single
atomic snapshot*. You can't put pg_xlog or selected tablespaces on
a separate filesystem that has a separate snapshot and expect the
various snapshot to be combined to be used as a coherent backup
unless you are archiving WAL and use pg_start_backup() (before the
first snapshot is initiated) and pg_stop_backup() (after the last
snapshot is completes) to take a PITR-style recovery.



Be sure to follow all the rules for PITR-style backup and recovery,
like deleting the postmaster.pid file and all files under pg_xlog
before starting the recovery. And of course, do NOT delete the
backup_label file created by pg_start_backup().
postgres  postgresql  atomic  snapshot  quiesce  database  db 
yesterday by theskett
Why am I getting pg_restore: [archiver] unsupported version (1.13) in file header error with pg_restore?
I get an error pg_restore: [archiver] unsupported version (1.13) in file header when I try to restore a dump file that was created using Heroku PGBackups (heroku pg:backups:capture or scheduled backups) feature or using pg_dump with one-off dynos.
heroku  postgresql  update  security 
yesterday by beery
HeidiSQL - MariaDB, MySQL, MSSQL and PostgreSQL made easy
HeidiSQL is a powerful and easy client for MariaDB, MySQL, Microsoft SQL Server and PostgreSQL. Open source and entirely free to use.
sql  rdbms  client  programming  mysql  mssql  postgresql  opensource  floss 
2 days ago by gilberto5757

« earlier    

related tags

1901  2019  @toread  administration  advice  amazon  api  app  apps  architecture  article  atomic  aurora  aws  backups  best_of  blog  blogs  book  books  cheatsheet  client  concurrency  css  data  database  databases  db  db2  dba  details  dev  devops  disk  distcomp  distributed-consensus  distributed  django  documentation  downloads  ec2  editor  engine  example  explain  flask  floss  free  freesoftware  git  github  gitlab  go  golang  graphql  grpahql  guardian  guide  guis  hash  heroku  howto  internal  internals  isolation  jan19  javascript  jobs  json  k  libraries  license.lgpl  links  lock  locks  mac_apps  md5  messaging  migrations  mongodb  mssql  multiengine  mysql  nodejsinteractive  npm  online  opensource  oracle  paid  papers  pdf  pelican  performance  pg  pitr  point-in-time-recovery  postgres  postgresweekly  productivity  profdev  programming  python  query  queues  quiesce  rdbms  redis  reference  replication  scalability  scaling  search  security  serializable  serverless  sidekiq  snapshot  software  space  spring  sql  sqlite  sqlserver  state  stremaing  swift-sh  swift  sysadmin  tech  terraform  toolkit  tools  toread  tornado.python  tradeoffs  transactions  trial  tutorial  unix  update  uuid  vacuum  wagtail  wal  wikientry  window  windows_apps 

Copy this bookmark:



description:


tags: