Re: Conflicting option checking in pg_restore

Hi On Sun, Oct 28, 2018 at 12:25 PM Fabien COELHO wrote: > > Hallå Daniel, > > > Checking for conflicting options in pg_restore was mostly done in main() > with > > one check deferred until RestoreArchive(). Reading the git history > makes it > > seem like it simply happened, without the disjoin

Re: PostgreSQL Limits and lack of documentation about them.

+1 for inclusion in docs. On Fri, Oct 26, 2018 at 4:00 AM David Rowley wrote: > For a long time, we documented our table size, max columns, max column > width limits, etc. in https://www.postgresql.org/about/ , but that > information seems to have now been removed. The last version I can > find

Re: Postgres restore issue

Hi Anand, I was unsuccessful in trying to reproduce this with a database and pg_dump from 8.3.7 and a pg_restore of 8.4.22. -- I do get the following error during the restore on an empty database,

Re: WAL archive (archive_mode = always) ?

Hi, I think what Takayuki is trying to say is that streaming replication works by sending the contents of the WAL archives to the standbys. If archive_mode was NOT set to always, and if you wanted to archive WAL logs in the standby you would need to rely on the process_command and make it ship the