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 1s9kqb-004uuR-Dr for pgsql-admin@arkaria.postgresql.org; Wed, 22 May 2024 12:13:35 +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 1s9kqa-00GU1o-Og for pgsql-admin@arkaria.postgresql.org; Wed, 22 May 2024 12:13:32 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s9kqZ-00GTzE-UN for pgsql-admin@lists.postgresql.org; Wed, 22 May 2024 12:13:32 +0000 Received: from mout-u-107.mailbox.org ([2001:67c:2050:101:465::107]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s9kqX-001Rpp-5Y for pgsql-admin@lists.postgresql.org; Wed, 22 May 2024 12:13:30 +0000 Received: from smtp1.mailbox.org (smtp1.mailbox.org [10.196.197.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-107.mailbox.org (Postfix) with ESMTPS id 4Vkqvj0LG2z9sV1; Wed, 22 May 2024 14:13:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ewie.name; s=MBO0001; t=1716380001; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=x03rVCJOLCAXcV82KyE/wb2w3rt8UAOyBdARZbcBlok=; b=HjBX6uyqfeRRu1BWOzjT36LdT7X7Hjh31Wa8VxD6t0LpCVh78rZtjWqlMJGT3Di3Zhgzta jPl+220xCXkyUiwk+W8Osd0bXyDNv44nDURXwZ6IdK2P0X+hLNyflsp5OZ/w4y0veukOKz BDJlfCI3f8VASwmgghJbm7k7sns+NlPQQZmjjZgG4tmMkGcR1KSOMMAIE6+qVCcu1E33NU RoGPor5eZjub5N4GpxaNtyanQZEzc31tXp5ix96+s8v0KYLIjHhwnreITe46aM6P7MhQFl LsZkIRHG44NR/M+mswB0ZtuKZjyjxeDksuFSQm4uduwUWT27qSEOykNdh7nJYw== Date: Wed, 22 May 2024 14:13:18 +0200 From: Erik Wienhold To: Luke Campbell Cc: pgsql-admin@lists.postgresql.org Subject: Re: displaying line breaks / increasing row height in pgadmin Message-ID: References: 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 Hi Luke, On 2024-05-22 13:46 +0200, Luke Campbell wrote: > Is there a way to make the results grid in pgadmin automatically increase > rows' height if a string contains a carriage return? > > I've updated pgadmin 4 to 8.6 and strings in the results grid now seem to > display line breaks / carriage returns by default, but this has caused me > to incorrectly think that was the end of the string. I would like these > strings to display as paragraphs or otherwise indicate that there's more > than what's displayed. This list is only about Postgres administration. PgAdmin has a separate list: https://www.postgresql.org/list/pgadmin-support/ -- Erik