Thanks for the explanation.
On Thu, Nov 23, 2023 at 10:55 AM Tom Lane wrote:
> Ron Johnson writes:
> > On Thu, Nov 23, 2023 at 3:37 AM Laurenz Albe
> > wrote:
> >> You can avoidwriting WAL if you set "wal_level = minimal", restart
> >> PostgreSQL
> >> and restore the dump with the
Ron Johnson writes:
> On Thu, Nov 23, 2023 at 3:37 AM Laurenz Albe
> wrote:
>> You can avoidwriting WAL if you set "wal_level = minimal", restart
>> PostgreSQL
>> and restore the dump with the --single-transaction option.
> Why does "--single-transaction" prevent WAL writes? I'd expect _more_
On Thu, Nov 23, 2023 at 3:37 AM Laurenz Albe
wrote:
[snip]
>
> You can avoidwriting WAL if you set "wal_level = minimal", restart
> PostgreSQL
> and restore the dump with the --single-transaction option.
>
Why does "--single-transaction" prevent WAL writes? I'd expect _more_
pg_wal growth from
On Wed, 2023-11-22 at 16:55 +, Efrain J. Berdecia wrote:
> Thanks, the issue we've run into, which I guess could be really a setup
> issue, with running a COPY command while executing pg_restore,
> is that if we are restoring a large table (bigger than 500GB) our WAL
> directory can grow to
On Wed, Nov 22, 2023 at 2:28 PM Tom Lane wrote:
> "Efrain J. Berdecia" writes:
> > Thanks, the issue we've run into, which I guess could be really a setup
> issue, with running a COPY command while executing pg_restore, is that if
> we are restoring a large table (bigger than 500GB) our WAL
"Efrain J. Berdecia" writes:
> Thanks, the issue we've run into, which I guess could be really a setup
> issue, with running a COPY command while executing pg_restore, is that if we
> are restoring a large table (bigger than 500GB) our WAL directory can grow to
> be very large.
> I would think
Thanks, the issue we've run into, which I guess could be really a setup issue,
with running a COPY command while executing pg_restore, is that if we are
restoring a large table (bigger than 500GB) our WAL directory can grow to be
very large.
I would think that if the pg_restore or COPY command
On 11/22/23 05:25, Efrain J. Berdecia wrote:
After working for a site where we are constantly doing logical pg_dump
to refresh environments I've come to miss features available in other
RDBMS' refresh/restore utilities.
Someone could point me in the right direction otherwise, but pg_restore
Thanks, I'm trying to gage the interest on such a feature enhancement.
Up to now I have not actively contributed to the Postgres Project but this is
itching my rusty programming fingers lol
Thanks,Efrain J. Berdecia
On Wednesday, November 22, 2023 at 08:28:18 AM EST, David G. Johnston
On Wednesday, November 22, 2023, Efrain J. Berdecia
wrote:
>
> Thanks in advance for any suggestions or the green light to post this to
> the PG-developer group :-)
>
If you aren’t offering up a patch for these it isn’t developer material and
belongs right here.
David J.
After working for a site where we are constantly doing logical pg_dump to
refresh environments I've come to miss features available in other RDBMS'
refresh/restore utilities.
Someone could point me in the right direction otherwise, but pg_restore seems
to be lacking the ability to resume a
11 matches
Mail list logo
