Hi Michael,
What's the support ticket that you've opened? I'd like to take a look and
help you get back up through that channel.
Thanks,
-Harold
Heroku Postgres
On Saturday, March 2, 2013 8:30:28 AM UTC-8, Michael wrote:
>
> I've not updated my database and forgot to move the app over as the He
Hi,
What goes on is that `pgbackups:restore` uses `pg_restore` behind the
scenes, with the `--clean` option. This option will remove any of the data
in your target database before restoring it, but the caveat is that it will
only do it for objects it will restore. If you have a table in your targe
Hello Jack,
The logs you are seeing are for queries taking longer than 50ms. We've
increased this from 50ms to 2s for Postgres version 9.2 because of the
useful pg_stat_statements view, a far better way to track slow or
problematic queries than tailing logs or searching through logs.
If you migra
On Mon, Sep 2, 2013 at 1:02 PM, ebdb wrote:
If I buy an add-on, does it apply to every app I'm running, or do I need to
> buy a separate copy for each app?
>
Each add-on is attached to an app. Typically you'll want one per
application (eg: one DB per app), and those are separate and distinct.
On Wednesday, October 23, 2013, Brian wrote:
> My local psql is not running on a standard port (company setup). Is there
> a way to instruct pg:pull to use a non-default port for the local db?
>
You can specify the port number as part of the URL using this format:
postgres://user:pass@localhost:
On Wed, Oct 23, 2013 at 9:29 AM, Brian wrote:
> I tried that but got this message: LOCAL_TARGET_DATABASE is not a valid
> database name
>
Oh I see. Sorry, I spoke too soon on my other response.
It's not documented exactly obvious, but any of the environment variables
available to libpq[1] can b
Hi Brian,
On Sat, Nov 2, 2013 at 7:04 PM, Brian wrote:
> could not connect to server: Connection refused
> Is the server running on host "localhost" (::1) and accepting
> TCP/IP connections on port 5432?
> could not connect to server: Connection refused
> Is the server running on host "localhos
PORT=15432 heroku pg:pull HEROKU_POSTGRESQL_ROSE local_db -a appname
>
>
>
> On Tuesday, November 5, 2013 12:43:07 AM UTC-5, Harold Giménez wrote:
>>
>>
>> Hi Brian,
>>
>> On Sat, Nov 2, 2013 at 7:04 PM, Brian wrote:
>>
>>> could not connect t
Are you doing anything to track and know whether the DB is the
bottleneck? I'd recommend tracking heroku postgres metrics[0] in
librato and try and find correlation. What DB plan are you using?
[0] https://devcenter.heroku.com/articles/heroku-postgres-metrics-logs
On Wed, Mar 26, 2014 at 10:47 AM
Hey Jack,
A common approach in ruby apps is using the Octopus gem. An approach
to making it work seamlessly on Heroku can be found on Dev Center:
https://devcenter.heroku.com/articles/distributing-reads-to-followers-with-octopus
-Harold
On Mon, Mar 31, 2014 at 11:29 AM, Jack Royal-Gordon wrote:
10 matches
Mail list logo
