On Fri, 2023-06-02 at 11:36 -0700, Joe Carlson wrote:
> I have SQL that does it with \copy (select * from where…) … And that
> is fine.
> But it would be nice to be able to run the \copy commands in parallel.
> So I was thinking of writing a background worker.
Why don't you go the easy way of us
On 6/2/23 18:06, Ron wrote:
On 6/2/23 19:58, Adrian Klaver wrote:
On 6/2/23 17:44, Ron wrote:
Ran into this when upgrading from 13.11 to 15.3...
The pg_restore phase failed with "ERROR: out of shared memory", and
recommended that I increase max_locks_per_transaction. Doing so let
the process
> On Jun 2, 2023, at 17:44, Ron wrote:
> Is this to be expected of such a huge schema?
pg_upgrade time is pretty much proportional to the number of database objects
in the schema, so a much larger schema taking much longer is to be expected.
On 6/2/23 19:58, Adrian Klaver wrote:
On 6/2/23 17:44, Ron wrote:
Ran into this when upgrading from 13.11 to 15.3...
The pg_restore phase failed with "ERROR: out of shared memory", and
recommended that I increase max_locks_per_transaction. Doing so let the
process run to completion.
It took
On 6/2/23 17:44, Ron wrote:
Ran into this when upgrading from 13.11 to 15.3...
The pg_restore phase failed with "ERROR: out of shared memory", and
recommended that I increase max_locks_per_transaction. Doing so let the
process run to completion.
It took 12.5 minutes to upgrade a 13GB instan
Ran into this when upgrading from 13.11 to 15.3...
The pg_restore phase failed with "ERROR: out of shared memory", and
recommended that I increase max_locks_per_transaction. Doing so let the
process run to completion.
It took 12.5 minutes to upgrade a 13GB instance. Soon after, I upgraded a
Hace you taken a look at dbt (https://www.getdbt.com/)? It's aimed at
analytics but can be used for any purpose.
Regards,
Guillermo González de Agüero
El vie, 2 jun 2023 15:36, Oliver Kohll escribió:
> Hi,
>
> Just wondering, does anyone else create apps which might not have 'big'
> data, but
Hi Folks,
I’m writing a little utility for dumping parts of tables into files which will
be later slurped into another primary instance. The primary source is our
referential data (big, and subject to heavy loads when adding data), the second
is a smaller version used in driving our web app. (s
On Fri, Jun 2, 2023, 09:36 Oliver Kohll wrote:
> Hi,
>
> Just wondering, does anyone else create apps which might not have 'big'
> data, but quite complex arrangements of views joining to each other?
>
> If so, do you have scripts to aid refactoring them e.g. drop/recreate/test
> them in the righ
Hi,
Just wondering, does anyone else create apps which might not have 'big'
data, but quite complex arrangements of views joining to each other?
If so, do you have scripts to aid refactoring them e.g. drop/recreate/test
them in the right order etc.?
I'm really impressed with the way Postgres han
On 5/30/23 10:05 PM, David Rowley wrote:
My understanding had been that concurrency was required, but I see the
commit message for 00d1e02be mentions:
Even single threaded
COPY is measurably faster, primarily due to not dirtying pages while
extending, if supported by the operating system (see
"=?ISO-8859-1?B?V2VuIFlp?=" <896634...@qq.com> writes:
> I don't know why are there many extra spaces in the output, and why the error
> message 'syntax error' is showed.
You didn't say exactly what you typed at it, but:
Your flex lexer lacks actions for many possible input characters,
notably s
12 matches
Mail list logo
