Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sS5j0-003w8J-BR for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Jul 2024 02:09:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sS5iy-00312e-I1 for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Jul 2024 02:09:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sS5iy-00312V-6I for pgsql-hackers@lists.postgresql.org; Fri, 12 Jul 2024 02:09:28 +0000 Received: from mail-il1-x12b.google.com ([2607:f8b0:4864:20::12b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sS5ir-001eTT-Mj for pgsql-hackers@postgresql.org; Fri, 12 Jul 2024 02:09:27 +0000 Received: by mail-il1-x12b.google.com with SMTP id e9e14a558f8ab-3737dc4a669so6223065ab.0 for ; Thu, 11 Jul 2024 19:09:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1720750159; x=1721354959; darn=postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=TAUlGrxVUmKv2fcFqFp9D0s4HSxj+zhgANex8G7To8E=; b=CnBTfdvb93sVh8nkA7eXtq793++FF8cl9H7cvds8qpj8dZfagTMXB20IJMxCXAqUjF C9R5Q7O23h9159CGmNib/s+x+GfuC/3TZjbLhOJ4du9JLjpKy3uGI6Uha27e0OP7KoHN TpvaQ+ZnWW+baMEArHDtsV0jfOgSfMe45Ss9AIscxDU2KtFk71GVrhOOCkJg5kGEIh70 dmMobbxFmnHpdYHp1lH3uM5AxH4XexcYvpMFi+ri3yDemGHzwreDBQ9y2Fo/8JxBYbdu /ImklJeErXy+Jteyw0nTqFNAMMZNXklBy8VdUHKrXJjOP4oej+2cMSBj4ZwcxEZDIlTT EATA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720750159; x=1721354959; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=TAUlGrxVUmKv2fcFqFp9D0s4HSxj+zhgANex8G7To8E=; b=DaVschkmJHXuOKqU/qYSOytWF25lRZNLh5vbAKqzfdrVv8fh40lAw5QDPcBoZ0rLqY aGlQN+w+vTBFVfwIXc/2i8DOnYWofYT/pzckUt4UeNYFskahrUievFmHQagWVzMPg6nc pH0FFQcbHRCPXZw+K7wBdweDLEmm8AcHNdMZaeu+KW0IjJtQkcp+UM4AMGq7R29PDmRd tyyc+DahanHcJ5V2Ag60YFywHhOwSWSdSpG67L6oZRktguziEWIXqPyWa54lHtCmnN7O P7tnhwrA9i+I8ZIRdZfnn7rF2lglc/2oFXeC0kUrMZkheIplezc+VTWXjVUFkKobf+MM NKIw== X-Gm-Message-State: AOJu0Yxhd+6Ycvr/REVAjLQkCnW8uKFW0cIYbVpzGQFNzuisgL7adQJE tAf4LsW7WAaz3TU+bs/9bar55335AvRSNYT4eleTrZ98nVRQoNAIciFsEg== X-Google-Smtp-Source: AGHT+IEUqSkmws9/eA/dIqMXwc7K2psKdotocOEcki6yaXCv166LcZH9Fd70+d5ftoWeXpwE8lpjgw== X-Received: by 2002:a05:6e02:1385:b0:375:873a:aa99 with SMTP id e9e14a558f8ab-38a592f4d70mr131633745ab.25.1720750159603; Thu, 11 Jul 2024 19:09:19 -0700 (PDT) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id e9e14a558f8ab-38a4b870711sm17391405ab.70.2024.07.11.19.09.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 11 Jul 2024 19:09:19 -0700 (PDT) Date: Thu, 11 Jul 2024 21:09:17 -0500 From: Nathan Bossart To: Euler Taveira Cc: pgsql-hackers Subject: Re: improve performance of pg_dump with many sequences Message-ID: References: <20240503025140.GA1227404@nathanxps13> <0a0f4d52-ab75-4d69-abe8-5713bf70eee6@app.fastmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Jul 10, 2024 at 11:52:33PM -0300, Euler Taveira wrote: > On Wed, Jul 10, 2024, at 7:05 PM, Nathan Bossart wrote: >> Unfortunately, I think we have to keep this workaround since older minor >> releases of PostgreSQL don't have the fix. > > Hmm. Right. On second thought, maybe we should just limit this improvement to the minor releases with the fix so that we _can_ get rid of the workaround. Or we could use the hacky workaround only for versions with the bug. -- nathan