On 18.03.14 02:32, Joe Conway wrote:
> On 03/17/2014 05:55 PM, Jeff Janes wrote:
>> On Mon, Mar 17, 2014 at 5:48 PM, Craig Ringer
>>
>> LOCK TABLE table1, table2, table3, ...
>
>> would help, instead of doing individual statements?
>
>> If I recall correctly, someone did submit a patch to do th
On 18.03.14 00:15, Tom Lane wrote:
> Jim Nasby writes:
>> On 3/17/14, 8:47 AM, Tom Lane wrote:
>>> (Note that this is only one of assorted O(N^2) behaviors in older versions
>>> of pg_dump; we've gradually stamped them out over time.)
>
>> On that note, it's recommended that when you are taking a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/17/2014 05:55 PM, Jeff Janes wrote:
> On Mon, Mar 17, 2014 at 5:48 PM, Craig Ringer
>
> LOCK TABLE table1, table2, table3, ...
>
> would help, instead of doing individual statements?
>
> If I recall correctly, someone did submit a patch to do
On Mon, Mar 17, 2014 at 5:48 PM, Craig Ringer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/18/2014 07:20 AM, Joe Conway wrote:
> > On 03/17/2014 04:15 PM, Tom Lane wrote:
> >> Jim Nasby writes:
> >>> On 3/17/14, 8:47 AM, Tom Lane wrote:
> (Note that this is only one of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/18/2014 07:20 AM, Joe Conway wrote:
> On 03/17/2014 04:15 PM, Tom Lane wrote:
>> Jim Nasby writes:
>>> On 3/17/14, 8:47 AM, Tom Lane wrote:
(Note that this is only one of assorted O(N^2) behaviors in
older versions of pg_dump; we've g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/17/2014 04:15 PM, Tom Lane wrote:
> Jim Nasby writes:
>> On 3/17/14, 8:47 AM, Tom Lane wrote:
>>> (Note that this is only one of assorted O(N^2) behaviors in
>>> older versions of pg_dump; we've gradually stamped them out
>>> over time.)
>
>> O
Jim Nasby writes:
> On 3/17/14, 8:47 AM, Tom Lane wrote:
>> (Note that this is only one of assorted O(N^2) behaviors in older versions
>> of pg_dump; we've gradually stamped them out over time.)
> On that note, it's recommended that when you are taking a backup to restore
> into a newer version
On 3/17/14, 8:47 AM, Tom Lane wrote:
Pavel Stehule writes:
2014-03-17 12:52 GMT+01:00 Jürgen Strobel :
I've googled the problem and there seem to be more people with similar
problems, so I made this a command line option --no-table-locks and
wrapped it up in as nice a patch against github/mas
Pavel Stehule writes:
> 2014-03-17 12:52 GMT+01:00 Jürgen Strobel :
>> I've googled the problem and there seem to be more people with similar
>> problems, so I made this a command line option --no-table-locks and
>> wrapped it up in as nice a patch against github/master as I can manage
>> (and I
2014-03-17 12:52 GMT+01:00 Jürgen Strobel :
>
> Hi,
>
> at work at my company I inherited responsibility for a large PG 8.1 DB,
> with a an extreme number of tables (~30). Surprisingly this is
> working quite well, except for maintenance and backup. I am tasked with
> finding a way to do dump
On Mon, Mar 17, 2014 at 7:52 AM, Jürgen Strobel wrote:
> at work at my company I inherited responsibility for a large PG 8.1 DB,
> with a an extreme number of tables (~30). Surprisingly this is
> working quite well, except for maintenance and backup. I am tasked with
> finding a way to do dump
Hi,
at work at my company I inherited responsibility for a large PG 8.1 DB,
with a an extreme number of tables (~30). Surprisingly this is
working quite well, except for maintenance and backup. I am tasked with
finding a way to do dump & restore to 9.3 with as little downtime as
possible.
Us
12 matches
Mail list logo
