On Fri, 26 Jan 2024 01:52:58 +0530 Atul Kumar wrote:
>Is the server running locally and accepting connections on that
>socket?
Maybe this will help:
# ss -l | grep 5432
On Thu, 14 Dec 2023 13:10:16 -0500 Ron Johnson wrote:
>> I'm not sure if you kept the line, but you have ellipsed-out ( is that
>> a word? )
ellipse: curve
ellipsis: ...
I need to follow my own advice: slow-down and you'll go faster...
Logged in as "postgres" (superuser). I see regexp_replace(); but not if
logged in as a read-only user...
So this is a permissions issue... I just discovered that a RO user with
only SELECT permision can run a query using regexp_re
On Sat, 11 Nov 2023 17:10:29 -0800 Adrian Klaver wrote:
>On 11/11/23 17:04, p...@pfortin.com wrote:
>> On Sat, 11 Nov 2023 16:53:01 -0800 Adrian Klaver wrote:
>>
>>> On 11/11/23 16:25, p...@pfortin.com wrote:
>>> Reply to list also
>>> Ccing list
On Sat, 11 Nov 2023 16:16:20 -0800 Adrian
On Sat, 11 Nov 2023 16:53:01 -0800 Adrian Klaver wrote:
>On 11/11/23 16:25, p...@pfortin.com wrote:
>Reply to list also
>Ccing list
>> On Sat, 11 Nov 2023 16:16:20 -0800 Adrian Klaver wrote:
>>
>
>>> Probably because it is spelled regexp_replace ().
>>
>> OK, found it in pg_catalog; but "cr
Hi,
PostgreSQL 15.4 on x86_64-mageia-linux-gnu, compiled by gcc (Mageia
12.3.0-3.mga9) 12.3.0, 64-bit
(the distro which can't figure out how to provide pgAdmin4)
Aren't all the functions listed in
https://www.postgresql.org/docs/current/functions-string.html
assumed to be included in a base insta
On Sun, 29 Oct 2023 16:16:05 +0100 Peter J. Holzer wrote:
>On 2023-10-29 09:21:46 -0400, p...@pfortin.com wrote:
>> These are all static tables. Does PG maintain a table row count so as to
>> avoid having to count each time?
>
>No. To count the rows in a table, Postgres has to actually read the
On Sun, 29 Oct 2023 16:00:46 +0100 Peter J. Holzer wrote:
>On 2023-10-27 19:46:09 -0400, p...@pfortin.com wrote:
>> On Fri, 27 Oct 2023 19:07:11 +0200 Peter J. Holzer wrote:
>> >Have you looked at the query plans as I recommended? (You might also
>> >want to enable track_io_timing to get extra i
On Sat, 28 Oct 2023 18:34:50 -0400 Jim Mlodgenski wrote:
Looking like a GOLD star for Jim...
>On Fri, Oct 27, 2023 at 7:46 PM wrote:
>
>> Memory: 125.5 GiB of RAM
>>
>It looks like you have a large amount of memory allocated to the server
>
>But your plans are doing reads instead of pulling th
On Fri, 27 Oct 2023 21:21:18 -0700 Adrian Klaver wrote:
>On 10/27/23 16:46, p...@pfortin.com wrote:
>> Peter,
>>
>> Thanks for your patience; I've been feeling pressure to get this
>> resolved; so have been lax in providing info here.. Hope the following
>> helps...
>>
>
>
>> Something I hadn
Peter,
Thanks for your patience; I've been feeling pressure to get this
resolved; so have been lax in providing info here.. Hope the following
helps...
On Fri, 27 Oct 2023 19:07:11 +0200 Peter J. Holzer wrote:
>On 2023-10-26 22:03:25 -0400, p...@pfortin.com wrote:
>> Are there any extra PG low
On Thu, 26 Oct 2023 15:50:16 -0400 p...@pfortin.com wrote:
>Hi Peter,
>
>All of the following is based on using SQL_workbench/J (WB) (Mageia Linux
>has not provided a viable pgAdmin4 package); WB is setup to autoload the
>table row count and 10 rows. I'm sticking to one set of files where they
>a
Hi Peter,
All of the following is based on using SQL_workbench/J (WB) (Mageia Linux
has not provided a viable pgAdmin4 package); WB is setup to autoload the
table row count and 10 rows. I'm sticking to one set of files where they
are all roughly 33.6M rows.
I've been doing a lot of digging and f
After much searching, I eventually discovered that there's a firmware
update for my Samsung Firecuda NVMe drives:
https://www.seagate.com/support/downloads/
Also Seagate:
https://www.dell.com/en-us/shop/workstations-isv-certified/sr/workstations/linux?appliedRefinements=39332
Not sure about the
On Mon, 23 Oct 2023 16:31:30 -0700 Adrian Klaver wrote:
>Please reply to list also.
>Ccing the list for this post.
Sorry, got the list's message and one directly from you; looks like I
picked the wrong one to reply to...
I just heard from a remote team member who wrote this:
!! Eventually fo
Forgot to mention version:
PostgreSQL 15.4 on x86_64-mageia-linux-gnu, compiled by gcc (Mageia
12.3.0-3.mga9) 12.3.0, 64-bit
Sorry,
Pierre
On Mon, 23 Oct 2023 15:09:16 -0500 Ken Marshall wrote:
>> Hi,
>>
>> I have a 1.6TB database with over 330 tables on a 4TB NVMe SSD. All
>> tables are static (no updates); most in 8M and 33M row sizes. Queries have
>> been great, until recently.
>
>> Also attached is the relevant system journal
Hi,
I have a 1.6TB database with over 330 tables on a 4TB NVMe SSD. All
tables are static (no updates); most in 8M and 33M row sizes. Queries have
been great, until recently.
I use SQL-workbench/J (WB) and starting at any table, if I use up/down
arrow to switch to another table, all that happens
Hi Adrian & Tom,
On Sat, 30 Sep 2023 15:57:32 -0700 Adrian Klaver wrote:
>On 9/30/23 14:54, p...@pfortin.com wrote:
>> On Sat, 30 Sep 2023 13:40:37 -0700 Adrian Klaver wrote:
>>
>>> On 9/30/23 11:32, p...@pfortin.com wrote:
>
>>
>> As I told Tom, the "test" DB has this issue; the producti
On Sat, 30 Sep 2023 13:40:37 -0700 Adrian Klaver wrote:
>On 9/30/23 11:32, p...@pfortin.com wrote:
>> On Sat, 30 Sep 2023 13:20:14 -0400 Tom Lane wrote:
>>
>
>> As vanilla as it gets... Standard locale (C). The only odd thing that
>> happened: a system update the other day installed and started
On Sat, 30 Sep 2023 13:20:14 -0400 Tom Lane wrote:
>p...@pfortin.com writes:
>> Python script and sample file attached...
>
>This runs fine for me, both in HEAD and 15.4.
>
>(Well, it fails at the last GRANT, seemingly because you wrote
>"{table}" not "{TABLE}". But the COPY goes through fine.)
On Sat, 30 Sep 2023 08:50:45 -0700 Adrian Klaver wrote:
>On 9/30/23 07:01, p...@pfortin.com wrote:
>> Hi Adrian,On Fri, 29 Sep 2023 14:27:48 -0700 Adrian Klaver wrote:
>>
>>> On 9/29/23 1:37 PM, p...@pfortin.com wrote:
Hi,
>
>>> I'm going to say it is the
>>>
>>> ( -- import only a sub
On Fri, 29 Sep 2023 18:21:02 -0400 Tom Lane wrote:
>p...@pfortin.com writes:
>> As a test, rather than use INSERT, I recently wrote a python test script
>> to import some 8M & 33M record files with COPY instead. These worked with
>> last weekend's data dump. Next, I wanted to look into importing
Hi Adrian,On Fri, 29 Sep 2023 14:27:48 -0700 Adrian Klaver wrote:
>On 9/29/23 1:37 PM, p...@pfortin.com wrote:
>> Hi,
>>
>> select version();
>> PostgreSQL 15.4 on x86_64-mageia-linux-gnu,
>> compiled by gcc (Mageia 12.3.0-3.mga9) 12.3.0, 64-bit
>>
>> As a test, rather than use INSERT, I recently
Hi,
select version();
PostgreSQL 15.4 on x86_64-mageia-linux-gnu,
compiled by gcc (Mageia 12.3.0-3.mga9) 12.3.0, 64-bit
As a test, rather than use INSERT, I recently wrote a python test script
to import some 8M & 33M record files with COPY instead. These worked with
last weekend's data dump. Ne
On Tue, 1 Aug 2023 06:22:46 -0400 Amn Ojee Uw wrote:
>"/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory*//*
Like mine, your distro probably uses /tmp/.s.PGSQL.5432
$ ll /tmp/.s.PGSQL.5432
srwxrwxrwx 1 postgres postgres 0 Aug 1 06:33 /tmp/.s.PGSQL.5432=
https://askubuntu.co
On Sun, 9 Jul 2023 16:42:15 -0700 David G. Johnston wrote:
>Yes, the mechanics of defining multi-column unique constraints on tables is
>covered in the docs.
Good to know I'm not searching in vain...
On Sun, 9 Jul 2023 17:04:03 -0700 Adrian Klaver wrote:
>On 7/9/23 15:58, p...@pfortin.com wrote:
>> Hi,
>>
>> Trying to figure out how to insert new property addresses into an
>> existing table.
>>
>> Can a UNIQUE constraint be applied to an entire row? Adding UNIQUE to
>> each column won't wor
Hi,
Trying to figure out how to insert new property addresses into an
existing table.
Can a UNIQUE constraint be applied to an entire row? Adding UNIQUE to
each column won't work in such a case since there are multiple properties
* on the same street
* in the same town
* with the same number on
On Thu, 29 Jun 2023 20:27:59 -0700 David G. Johnston wrote:
>On Thu, Jun 29, 2023 at 7:42 PM wrote:
>
>> Trying to write a script that will run on Linux, Windows, and Mac.
>>
>
>This seems impossible on its face unless you use WSL within the Windows
>environment. And if you are doing that, the
On Fri, 30 Jun 2023 11:16:36 +0800 Julien Rouhaud wrote:
>Hi,
>
>On Thu, Jun 29, 2023 at 10:42:00PM -0400, p...@pfortin.com wrote:
>>
>> Windows: %APPDATA%\postgresql\pgpass.conf
>>
>> On Linux, this works. However, on Windows, psql will not read
>> pgpass.conf (tried in just about every location
Hi,
Trying to write a script that will run on Linux, Windows, and Mac.
The "standard" credentials file contains:
hostname:port:database:username:password
in:
Linux: .pgpass
Windows: %APPDATA%\postgresql\pgpass.conf
Mac: (I'm not there yet...)
On Linux, this works. However, on Windows,
On Mon, 20 Feb 2023 15:24:23 -0800 Adrian Klaver wrote:
>On 2/20/23 11:36, p...@pfortin.com wrote:
>> On Mon, 20 Feb 2023 11:06:34 -0800 Adrian Klaver wrote:
>>
>>> On 2/20/23 10:27, p...@pfortin.com wrote:
[Still a newbie; but learning fast...]
Hi,
>
>>
>> Notwithstanding t
On Mon, 20 Feb 2023 11:06:34 -0800 Adrian Klaver wrote:
>On 2/20/23 10:27, p...@pfortin.com wrote:
>> [Still a newbie; but learning fast...]
>>
>> Hi,
>>
>> A remote team member is helping out by dumping some of his tables via
>> pgAdmin4 on Windows. My DB is on Linux.
>>
>> The other day, I r
[Still a newbie; but learning fast...]
Hi,
A remote team member is helping out by dumping some of his tables via
pgAdmin4 on Windows. My DB is on Linux.
The other day, I restored his first file with:
pg_restore --host "localhost" --port "5432" --username "postgres"
--no-password --dbname "m
nly after getting to a point of "no
return". The documentation alludes to checking everything before
proceeding; but it's the story of my life to find the unexpected...
[postgres@pf ~]$ /usr/bin/pg_upgrade -b /usr/local/pgsql/bin -B /usr/bin
-d /mnt/work/var/lib/pgsql/data13 -D /mn
gt;
>Looks like this is what I was trying to be certain of... Thanks!!
>Pierre
Sigh... I thought all was good... This was not expected and is not
discussed in the pg_upgrade instructions:
[postgres@pf ~]$ /usr/bin/pg_upgrade -b /usr/local/pgsql/bin -B /usr/bin
-d /mnt/work/var/lib/pgsql/d
On Sun, 15 Jan 2023 15:59:20 -0500 Tom Lane wrote:
>p...@pfortin.com writes:
>> On Sun, 15 Jan 2023 14:47:35 -0500 Tom Lane wrote:
>>> I think you misunderstand how this is supposed to work. The -D
>>> argument should point at an *empty* data directory that has been
>>> freshly initialized with
27;m fairly new to postgres; but have databases with about 2TB of data.
>>>>
>>>> Trying to upgrade from 13.6 to 15.1, pg_upgrade complains with:
>>>> [postgres@pf ~]$ /usr/bin/pg_upgrade -b /usr/local/pgsql/bin -B /usr/bin \
>>>> -d /mnt/db/var/lib/
On Sun, 15 Jan 2023 12:23:10 -0800 Adrian Klaver wrote:
>On 1/15/23 11:27, p...@pfortin.com wrote:
>> Hi,
>>
>> I'm fairly new to postgres; but have databases with about 2TB of data.
>>
>> Trying to upgrade from 13.6 to 15.1, pg_upgrade complains with:
>
On Sun, 15 Jan 2023 14:47:35 -0500 Tom Lane wrote:
>p...@pfortin.com writes:
>> Trying to upgrade from 13.6 to 15.1, pg_upgrade complains with:
>> [postgres@pf ~]$ /usr/bin/pg_upgrade -b /usr/local/pgsql/bin -B /usr/bin \
>> -d /mnt/db/var/lib/pgsql/data -D /mnt/wo
Hi,
I'm fairly new to postgres; but have databases with about 2TB of data.
Trying to upgrade from 13.6 to 15.1, pg_upgrade complains with:
[postgres@pf ~]$ /usr/bin/pg_upgrade -b /usr/local/pgsql/bin -B /usr/bin \
-d /mnt/db/var/lib/pgsql/data -D /mnt/work/var/lib/pgsql/data \
-s /t
42 matches
Mail list logo
