Command: heroku pgbackups:capture --remote production
Response: >>> HEROKU_POSTGRESQL_COLOR_URL (DATABASE_URL) ----backup---> a712
Command: heroku pgbackups:url [db_key] --remote production
| { | |
| "AL": "Alabama", | |
| "AK": "Alaska", | |
| "AS": "American Samoa", | |
| "AZ": "Arizona", | |
| "AR": "Arkansas", | |
| "CA": "California", | |
| "CO": "Colorado", | |
| "CT": "Connecticut", | |
| "DE": "Delaware", |
| import { Injectable } from 'angular2/core'; | |
| import { Storage } from './storage'; | |
| import { CurrentUser } from '../interfaces/common'; | |
| @Injectable() | |
| export class Authentication{ | |
| private _storageService : Storage; | |
| private _userKey : string = "CURRENT_USER"; | |
| constructor(storageService : Storage){ |
The connection failed because by default psql connects over UNIX sockets using peer authentication, that requires the current UNIX user to have the same user name as psql. So you will have to create the UNIX user postgres and then login as postgres or use sudo -u postgres psql database-name for accessing the database (and psql should not ask for a password).
If you cannot or do not want to create the UNIX user, like if you just want to connect to your database for ad hoc queries, forcing a socket connection using psql --host=localhost --dbname=database-name --username=postgres (as pointed out by @meyerson answer) will solve your immediate problem.
But if you intend to force password authentication over Unix sockets instead of the peer method, try changing the following pg_hba.conf* line:
from
| http://www.youtube.com/watch?v=-wtIMTCHWuI | |
| http://youtube.com/watch?v=-wtIMTCHWuI | |
| http://m.youtube.com/watch?v=-wtIMTCHWuI | |
| https://www.youtube.com/watch?v=lalOy8Mbfdc | |
| https://youtube.com/watch?v=lalOy8Mbfdc | |
| https://m.youtube.com/watch?v=lalOy8Mbfdc | |
| http://www.youtube.com/watch?v=yZv2daTWRZU&feature=em-uploademail | |
| http://youtube.com/watch?v=yZv2daTWRZU&feature=em-uploademail | |
| http://m.youtube.com/watch?v=yZv2daTWRZU&feature=em-uploademail |
| 1. Go to C:\Users\<my_username>\AppData\Roaming and locate the .gitkraken folder | |
| 2. Inside this folder you can find a localRepoCache file. | |
| 3. Remove the entries that areunwanted/ duplicated, and restart the Gitkraken. |