Upgrade local eRegs DB to use Postgres 11

[patphongs]

Summary

What we're after:
The eRegs postgres databases in our cloud environment is now using postgress version 11. We need to make sure our local environment is running the same version, especially for those team members working on parsing eregs.

Related issues

• Update README, team postgres version to 10.7 openFEC#4332
• Upgrade local CMS DB to use Postgres 11 fec-cms#3757

Completion criteria

• Local eRegs database is running using Postgres V11

Tech steps or considerations

• Try running both Postgres V11 and Postgres V10.7 locally
• Run local eRegs database using Postgres V11

[pkfec]

Steps to install/setup postgres11 via homebrew:

1. Install pg11

• run brew install postgresql@11

2. Export postgresql v11 path to bash_profile

• run echo 'export PATH="/usr/local/opt/postgresql@11/bin:$PATH"' >> /Users/pkasireddy/.bash_profile

3. Start the pg11 service

• run brew services start postgresql@11

4. check if pg11 service is UP and running

• run brew services list

To test/parse eregs on local pg11 DB:

1. Instructions on how to run parser env: https://github.com/fecgov/fec-eregs#loading-fecs-regulations

2. On eregs repo activate python 3.6.1 virtual environment

• run pyenv activate eregs361

3. Create a test db

• run createdb eregs-test

4. Use a tool (pgadmin) or psql to connect to the test eregs db to confirm the eregs-test db is of PG v11

• run psql postgres :

5. Parser regs on local on eregs repo

• run python load_regs/load_fec_regs.py

6. Use a tool (pgadmin) or psql to connect to the test eregs db:

• Verify that the test eregs db PG v11.8.
  -- run SELECT version();
• Also check all 45 regs parsed by running the following script
  -- run SELECT count(*) FROM public.regcore_notice;

[pkfec]

On cloud.gov eregs shared DB version is PG 11. I have setup PG10 and PG11 on my local env and parse 2020 regs on my local without any issues. Testing is DONE. Hence closing this ticket