I made mistake in a filename in pg_dump command, i.e. have used path from
another server, which not exists on this one. pg_dump instead of checking
permissions / existence of output file first dumped the whole database and
at the end (after some time ... ) threw an error:
(...)
pg_dump: saving dat
Exactly, that's the twist I've decided after some tests yesterday (the
"lock all tables on last try" degraded performance in an obscene way):
giving up on serializable by default.
I wanted to use serializable so developers wouldn't have to worry about
properly using locks, but implementing thi
On Tue, Jul 7, 2015 at 12:10 AM, John R Pierce wrote:
> On 7/6/2015 9:55 PM, c.bu...@posteo.jp wrote:
>
>> On 2015-07-05 22:16 John R Pierce wrote:
>>
>>> >at a bare minimum, a database administrator needs to create database
>>> >roles (users) and databases for an app like yours.
>>>
>> The admi
On Tue, Jul 7, 2015 at 4:26 AM, pinker wrote:
> I made mistake in a filename in pg_dump command, i.e. have used path from
> another server, which not exists on this one. pg_dump instead of checking
> permissions / existence of output file first dumped the whole database and
> at the end (after so
John McKown wrote
> What version of PostgreSQL? What OS? What was the command line?
*OS*: Linux OptiPlex-760 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Linux Mint 15 Olivia
*pg_dump*: pg_dump (PostgreSQL) 9.4.1
*command line:*
opt/PostgreSQL/9.4/
On 07/07/2015 05:23 AM, pinker wrote:
John McKown wrote
What version of PostgreSQL? What OS? What was the command line?
*OS*: Linux OptiPlex-760 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Linux Mint 15 Olivia
*pg_dump*: pg_dump (PostgreSQL) 9.
Adrian Klaver-4 wrote
> So this was not the actual command you ran as I see no path specification.
>
> Some notes:
>
> 1) plain format is the default so it does not need to specified.
>
> 2) Either --inserts or --column-inserts not both. FYI this really slows
> down the restore process.
>
> 3)
On 7 July 2015 at 12:55, Filipe Pina wrote:
> On Ter, Jul 7, 2015 at 1:41 , Adrian Klaver
> wrote:
>> Still not sure what is you are trying to accomplish. Is it really necessary
>> that every transaction be serialized? Or to put it another way, why are you
>> running in serializable by default? O
On Ter, Jul 7, 2015 at 2:31 , Alban Hertroys wrote:
On 7 July 2015 at 12:55, Filipe Pina
wrote:
On Ter, Jul 7, 2015 at 1:41 , Adrian Klaver
wrote:
Still not sure what is you are trying to accomplish. Is it really
necessary
that every transaction be serialized? Or to put it another way,
On 07/07/2015 06:00 AM, pinker wrote:
Adrian Klaver-4 wrote
So this was not the actual command you ran as I see no path specification.
Some notes:
1) plain format is the default so it does not need to specified.
2) Either --inserts or --column-inserts not both. FYI this really slows
down the
On 07/07/2015 06:44 AM, Filipe Pina wrote:
On Ter, Jul 7, 2015 at 2:31 , Alban Hertroys wrote:
On 7 July 2015 at 12:55, Filipe Pina wrote:
On Ter, Jul 7, 2015 at 1:41 , Adrian Klaver
wrote:
Still not sure what is you are trying to accomplish. Is it
really necessary t
Adrian Klaver-4 wrote
> So how did you get the wrong file name then, the pgAdmin backup dialog
> has a file selector?
>
> Or did you cut and paste into the file field?
I've cut, pasted and changed parameters.
--
View this message in context:
http://postgresql.nabble.com/pg-dump-PostgreSQL-
Adrian Klaver-4 wrote
> So how did you get the wrong file name then, the pgAdmin backup dialog
> has a file selector?
>
> Or did you cut and paste into the file field?
Anyway, shouldn't postgresql first check if dump can be saved? and then
start doing it?
--
View this message in context:
htt
John McKown writes:
> On Tue, Jul 7, 2015 at 4:26 AM, pinker wrote:
>> I made mistake in a filename in pg_dump command, i.e. have used path from
>> another server, which not exists on this one. pg_dump instead of checking
>> permissions / existence of output file first dumped the whole database a
On Ter, Jul 7, 2015 at 2:51 , Adrian Klaver
wrote:
On 07/07/2015 06:44 AM, Filipe Pina wrote:
On Ter, Jul 7, 2015 at 2:31 , Alban Hertroys
wrote:
On 7 July 2015 at 12:55, Filipe Pina
wrote:
On Ter, Jul 7, 2015 at 1:41 , Adrian Klaver
wrote:
Still not sure what is you ar
On 07/07/2015 06:55 AM, pinker wrote:
Adrian Klaver-4 wrote
So how did you get the wrong file name then, the pgAdmin backup dialog
has a file selector?
Or did you cut and paste into the file field?
I've cut, pasted and changed parameters.
I was talking about when you ran the backup from pgA
On 07/07/2015 07:12 AM, pinker wrote:
Adrian Klaver-4 wrote
So how did you get the wrong file name then, the pgAdmin backup dialog
has a file selector?
Or did you cut and paste into the file field?
Anyway, shouldn't postgresql first check if dump can be saved? and then
start doing it?
pgAdm
On 07/07/2015 07:12 AM, pinker wrote:
Adrian Klaver-4 wrote
So how did you get the wrong file name then, the pgAdmin backup dialog
has a file selector?
Or did you cut and paste into the file field?
Anyway, shouldn't postgresql first check if dump can be saved? and then
start doing it?
Ignor
Adrian Klaver-4 wrote
> I was talking about when you ran the backup from pgAdmin. The backup
> dialog has a file selector button to select the path/file you want to
> back up to. So I was wondering how you got an incorrect path in the
> first place? Then it occurred to me you might not have hav
On 07/07/2015 08:15 AM, pinker wrote:
Adrian Klaver-4 wrote
I was talking about when you ran the backup from pgAdmin. The backup
dialog has a file selector button to select the path/file you want to
back up to. So I was wondering how you got an incorrect path in the
first place? Then it occurre
I recently upgraded to Ubuntu 15.04 with PostgreSQL 9.4.4 with uuids and
plv8 coffeescript extensions. I can access the database via psql. My web
application uses node.js via pg-bricks. It works perfectly on my Mac dev
machine.
On the server, I get this error:
preload failed { [Error: connect
21 matches
Mail list logo
