Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1jAzli-000133-J1 for pgsql-hackers@arkaria.postgresql.org; Sun, 08 Mar 2020 17:31:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jAzlh-0005fV-BX for pgsql-hackers@arkaria.postgresql.org; Sun, 08 Mar 2020 17:31:13 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1jAzlg-0005aZ-R3 for pgsql-hackers@lists.postgresql.org; Sun, 08 Mar 2020 17:31:13 +0000 Received: from mail-yw1-xc44.google.com ([2607:f8b0:4864:20::c44]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jAzlc-0000hH-Ip for pgsql-hackers@postgresql.org; Sun, 08 Mar 2020 17:31:11 +0000 Received: by mail-yw1-xc44.google.com with SMTP id d79so6691370ywd.2 for ; Sun, 08 Mar 2020 10:31:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :user-agent; bh=vGwwHIXFRegabM2HNC4DUOJIwi2RUDc9QqL1sS4Fb+Q=; b=riVoi/1w74U5fsjr9rMtMoxvORgI1qY4zt3NU4bIBalw6v2liT/MvCp4dyj99fk9FW CGgV6aymZsvsnDGYrTCQuaMhbXg10VplVWaikctGi6MyTcpkIcYOQzTsj8dofAqDuXBl BB2TO7tR+YNZH9kyQaSeOj1Oib9BIc6lIDbp9StRHt5oQ70z8cRoiJ/JMdyAAiTToaY2 z84y5OBo14UihU5c/45bZjvFxQcTd74jI5vPSKAd88sRaY0MzUBPfkS7pGaSDhnGANrn u02qRFmYOASR3qDaY4LHvPWBsEp2GZsIGeE9iOxX/Z1Z8th+JvyHKMcwj/kX9su01qLr CrAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:user-agent; bh=vGwwHIXFRegabM2HNC4DUOJIwi2RUDc9QqL1sS4Fb+Q=; b=qbodiJTuiSN+mPm5TS2nUylUbAgV2frhKcUQOq5758QXiCkFiVyCu1Zh375K+d6KgR wOxMK8updnGSPS0+E8NfRD62nJNHs+W19/Em+QgiggthQypkt5OfCu2p2ZnnS0GMpHBE K19UNz4209wXi+KFCZxNU7TfyzqoeKuWx6Fp3hd6hg4XvV1n5iP7PHj86lvJdmr9Rai0 XQvkV12TSPGLoRJtAcm+CYASdDPEpN4qEhF5w6vGkgI0fmzJwLDw79pxPCGCztNgTwxG Y9OCrpDaFtu++v0z8IJruvhADHeI3Q2PWOd3wFH12B2EI2/yzE7GnXj9Ct+3bqNHhOfX efxQ== X-Gm-Message-State: ANhLgQ1HLtZTHjtoadovuwNkliW5nGW00rSLC/QCte6Qsa9rwKEWJEJO rUrPl181p8NF9vCt2AgK34HZow== X-Google-Smtp-Source: ADFU+vst55YFNnK1ndDIUHkzkywh74idOk9Pica33634y+yzYqUJztZjcQ2fLjW9gTFm0yMhlkKb5g== X-Received: by 2002:a05:6902:702:: with SMTP id k2mr6911943ybt.127.1583688666659; Sun, 08 Mar 2020 10:31:06 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id w128sm16873967ywf.72.2020.03.08.10.31.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 08 Mar 2020 10:31:05 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id 1B166800827; Sun, 8 Mar 2020 12:31:04 -0500 (CDT) Date: Sun, 8 Mar 2020 12:31:03 -0500 From: Justin Pryzby To: pgsql-hackers@postgresql.org Cc: Fabien COELHO , Alvaro Herrera , David Steele , "Bossart, Nathan" , Thomas Munro Subject: pg11+: pg_ls_*dir LIMIT 1: temporary files .. not closed at end-of-transaction Message-ID: <20200308173103.GC1357@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk While working on a patch, I noticed this pre-existing behavior, which seems to be new since v11, maybe due to changes to SRF. |postgres=# SELECT pg_ls_dir('.') LIMIT 1; |WARNING: 1 temporary files and directories not closed at end-of-transaction |pg_ls_dir | pg_dynshmem |postgres=# SELECT pg_ls_waldir() LIMIT 1; |WARNING: 1 temporary files and directories not closed at end-of-transaction |-[ RECORD 1 ]+------------------------------------------------------------- |pg_ls_waldir | (00000001000031920000007B,16777216,"2020-03-08 03:50:34-07") Note, that doesn't happen with "SELECT * FROM". I'm not sure what the solution is to that, but my patch was going to make it worse rather than better for pg_ls_tmpdir. -- Justin