Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pHssy-0008Ey-0j for pgsql-general@arkaria.postgresql.org; Tue, 17 Jan 2023 20:48:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pHssv-0000r1-2Q for pgsql-general@arkaria.postgresql.org; Tue, 17 Jan 2023 20:48:45 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pHssu-0000qq-Mh for pgsql-general@lists.postgresql.org; Tue, 17 Jan 2023 20:48:44 +0000 Received: from mail-qt1-x82c.google.com ([2607:f8b0:4864:20::82c]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pHsss-0007EV-F1 for pgsql-general@lists.postgresql.org; Tue, 17 Jan 2023 20:48:43 +0000 Received: by mail-qt1-x82c.google.com with SMTP id r15so5048756qtx.6 for ; Tue, 17 Jan 2023 12:48:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:subject:from:content-language:to :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=xLzf65puFUbUF+K6UFsfE4P8OJzGtSTgXfiuZFTiVqI=; b=kotMY6ZMtpAdBWtiWx6kESRAkUV5/HEDv7d0wLmFrB2m2wVySErPPXFrRyQD9ErViV sBDep19oaXAcoI7fkhtZtXqsc7KeZMPApTXoGLH6c+gJBOTiMoHsclJYPTismq6xytOA GbFjDAm/DuPVqbuLVRzJBaX0ysnb9D3viIEdnYkztJKl5w16eSS+hQz67j4ZqP9dLJv1 s+fEtUmMhYINLMx5+j3uLfkLBF0EVDVMa14MInrPul71gG4IzlpthyYMgQX3ww5aomro mwiGgarP99zUbIuDVNOl9EWGEFw95BFRn9bCrtM051J8E3BIyW4TXi4rWPO96JrSBczE 68gA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:subject:from:content-language:to :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=xLzf65puFUbUF+K6UFsfE4P8OJzGtSTgXfiuZFTiVqI=; b=1DoEyu82NWXVlO8kob3/uI8mDdM+8io5iN4uYEID8kTanXHDjWGgercF4WsM9+UsZB HzdvEa9vAzFlaKy+hXCEJqJvegZX1tB1F9fO8cHffKM3Kb+V8veuj8x1GWcbqbJgh9Tq Tfvl/qBUgcz7p2YneXqqmjkpjjPUEdLZ+NASkKy/peMFx7dYBajE1e82KT1rkfKxqo1n dB4H7Fc/AYM5cBFy1yaVGkl4Bx1H+HOVyfwaX/pE2muGg6PIeoI17Qw6z896UkKShQ56 KUoWRUZGkQZeYVDBCGIBYtyqQTSfmPzByBMBqsFNi0sApoaK4ukX9jaivq8NzBvvShjh a3KA== X-Gm-Message-State: AFqh2kqWgKaSzPNICoZClKpaBwlLmbm6hAju1zvglJtLnzmIU2D8yv6w vtAbrhf1JNuRD02VSoZjU7GIG9A9Uls= X-Google-Smtp-Source: AMrXdXuMsnJZ4fG+4jWDYvqCB2TDMcx14ObkCImEQSCqDIgmeHTsxutHwJGuA7Cj0bs4ONWv+K1DpQ== X-Received: by 2002:ac8:670a:0:b0:3b6:2dc7:de7d with SMTP id e10-20020ac8670a000000b003b62dc7de7dmr5461902qtp.22.1673988521248; Tue, 17 Jan 2023 12:48:41 -0800 (PST) Received: from [192.168.1.66] (108-250-206-84.lightspeed.nworla.sbcglobal.net. [108.250.206.84]) by smtp.googlemail.com with ESMTPSA id p15-20020ac8460f000000b003ae33f9260dsm4501941qtn.49.2023.01.17.12.48.40 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 17 Jan 2023 12:48:40 -0800 (PST) Message-ID: <04db9247-4452-e9bb-e64a-1545e04d37bc@gmail.com> Date: Tue, 17 Jan 2023 14:48:40 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 To: pgsql-general@lists.postgresql.org Content-Language: en-US From: Ron Subject: Maintaining blank lines in psql output? Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk White space can of course make things easy to read, but psql seems to ignore those blank lines.  Is there any way to retain them in psql output? $ cat spaces.sql insert into foo values(1); insert into foo values(2); insert into foo values(3); insert into foo values(4); insert into bar values(1); insert into bar values(2); insert into bar values(3); insert into bar values(4); insert into snaggle values(1); insert into snaggle values(2); insert into snaggle values(3); insert into snaggle values(4); insert into frob values(1); insert into frob values(2); insert into frob values(3); insert into frob values(4); postgres@haggis:~$ psql12 test -af spaces.sql insert into foo values(1); INSERT 0 1 insert into foo values(2); INSERT 0 1 insert into foo values(3); INSERT 0 1 insert into foo values(4); INSERT 0 1 insert into bar values(1); INSERT 0 1 insert into bar values(2); INSERT 0 1 insert into bar values(3); INSERT 0 1 insert into bar values(4); INSERT 0 1 insert into snaggle values(1); INSERT 0 1 insert into snaggle values(2); INSERT 0 1 insert into snaggle values(3); INSERT 0 1 insert into snaggle values(4); INSERT 0 1 insert into frob values(1); INSERT 0 1 insert into frob values(2); INSERT 0 1 insert into frob values(3); INSERT 0 1 insert into frob values(4); INSERT 0 1 -- Born in Arizona, moved to Babylonia.