On Sun, 2025-01-05 at 22:18 -0500, Ron Johnson wrote:
> On Sun, Jan 5, 2025 at 7:27 PM Nick wrote:
> >
> > I have some questions about the
> > pgAdmin Debian package version.
> >
> > 1. If we're using the pgAdmin DEB repo, will `apt-update` always
>
g each time the setup playbook runs and updates PgAdmin.
Thanks,
Nick
>
> On Tue, Dec 31, 2024 at 10:32 PM Nick wrote:
> >
> > I'm trying to create an Ansible playbook that sets up and manages
> > Postgres on Debian 12.
> >
> > I'm having issues with the default username/login structure, and
> > could
> &
On Tue, 2024-12-31 at 23:16 +0100, Andreas 'ads' Scherbaum wrote:
>
>
>
> Can you please provide an example of the task(s) which fail?
> If you have passwordless "sudo" configured tor the user running
> Ansible,
> this works:
>
> - name: Ping PostgreSQL
> postgresql_ping:
> db: postgres
>
I'm trying to create an Ansible playbook that sets up and manages
Postgres on Debian 12.
I'm having issues with the default username/login structure, and could
use some help.
I'm installing the `postgresql` package via apt, and Debian creates a
`postgres` system account that has a locked passwo
The external SSD is an Orico drive that is connected with USB-C. It is
initialised as a GUID Partition Map with a single AFPS partition.
We have run PostgreSQL 15 and earlier, before upgrading to 16 when it came out
last year. We didn't have any problems with 16 until recently, after upgrading
to Sonoma.
Nick
On 22 Mar 2024, at 17:00, Alban Hertroys wrote:
On Fri, 22 Mar 2024 at 15:01, Nick Renders
wrote:
We now have a second machine with this issue: it is an Intel Mac mini
running macOS Sonoma (14.4) and PostgreSQL 16.2.
This one only has a single Data directory, so there are no multiple
On 13 Mar 2024, at 12:35, Stephen Frost wrote:
> Greetings,
>
> * Nick Renders (postg...@arcict.com) wrote:
>>> ...run them under different users on the system.
>>
>> Are you referring to the "postgres" user / role? Does that also mean setting
>> u
On 11 Mar 2024, at 16:04, Adrian Klaver wrote:
> On 3/11/24 03:11, Nick Renders wrote:
>> Thank you for your reply Laurenz.
>> I don't think it is related to any third party security software. We have
>> several other machines with a similar setup, but this is the onl
ur restore script and the issue did
not occur.
I have just performed another restore on cluster A and now cluster B is
throwing errors in the log again.
Any idea why this is happening? It does not occur with every restore, but it
seems to be related anyway.
Thanks,
Nick Renders
On 26 Feb 202
s of those 2 files are all in order.
When this happens, the server is no longer accessible, and we need to restart
the service (pg_ctl restart).
Once restarted, Popstgres runs fine again for a couple of days.
We are running PostgreSQL 16.2 on macOS 14.3.1.
Any idea what might be causing this issue, or how to resolve it?
Best regards,
Nick Renders
either, only when
it actually performs the job of committing the insert, if this fails, then
perform the `on conflict do nothing`. Therefore, due to the original merge
semantics, merge insert doesn't need to follow the same requirements as
normal `insert`, and it doesn't need to *wait* -
ion
In my opinion, it would be better for merge to offer the functionality to
simply ignore the rows that cause unique violation exceptions instead of
tanking the whole query.
Thank you,
Nick
On Sat, 30 Sept 2023, 23:37 Tom Lane, wrote:
>
> I think what you're asking for is a scheme whereby some rows in a
> table have datatype X in a particular column while other rows in
> the very same physical table have datatype Y in the same column.
>
An alternative for NOT NULL columns would be
t; -D "C:\Program Files\PostgreSQL\15\data" -w
> waiting for server to start2023-09-22 12:48:05.438 CDT [4796]
> FATAL: could
> not create lock file "postmaster.pid": Permission denied
>
--
Nick Ivanov
Solution Architect
www.enterprisedb.com
ched.
Any tips?
Thanks,
Nick Renders
To provide more complete information:
Here is the name and version of each extension we have installed:
azure (1.0)
btree_gin (1.3)
citext (1.6)
pgcrypto (1.3)
plpgsql (1.0)
uuid-ossp (1.1)
This email and any attachments thereto may contain private, confidential, and
privileged material fo
Hello Tom,
Thanks for the information. Here are the extensions we are using:
uuid-ossp
pgcrypto
citext
btree_gin
The warnings did start emitting shortly after the installation of btree_gin, so
it seems somewhat suspect
From: Tom Lane
Date: Thursday, May 18, 2023 at 11:30 AM
To: Arora, Nick
We are using PostgreSQL 12.13. We are noticing that queries that attempt to
retrieve an element of an array by specifying its position cause a warning to
be emitted: "WARNING: unrecognized node type: 110".
Would appreciate your help diagnosing the issue and identifying steps to
resolve.
Queri
On Thu, 12 May 2022 at 14:48, Tom Lane wrote:
> "Zwettler Markus (OIZ)" writes:
> > I don't want to do use the normal backup algorithm where pg_start_backup
> + pg_stop_backup will fix any fractured block and I am required to have all
> archived logfiles, therefore.
> > I want to produce an atom
On Mon, 25 Apr 2022 at 12:45, Laurenz Albe wrote:
>
> You could consider upgrade in several steps:
>
> - pg_upgrade to v14 on the current operating system
> - use replication, than switchover to move to a current operating system
> on a different
> machine
> - REINDEX CONCURRENTLY all indexes o
On Thu, 14 Apr 2022 at 10:47, Steve Baldwin wrote:
> Ok, so you want to allow _other_ updates to a customer while this process
> is happening? In that case, advisory locks will probably work. The only
> consideration is that the 'id' is a bigint. If your customer id maps to
> that, great. If not
On Mon, 6 Dec 2021 at 18:48, Phil Endecott
wrote:
>
> - I have a raw data table, indexed on a timestamp column, to which
> new data is regularly being added.
>
> - I have a set of views that produce hourly/daily/monthly summaries
> of this data. Querying these views is slow, so I'd like to mak
ts in the same error.
I see now that our original pg_restore script does not include the -h
parameter. Somehow, it has snuck in my commands when testing Postgres
14. That might mean that the same issue exists in previous versions as
well. I will investigate further.
Nick
On 15 Oct 2021, at 1
d familiar to anyone? Is it an issue with the new Postgres
14 release, or is there something else that might be causing this?
Best regards,
Nick Renders
set it to "trust", the command goes through just
fine.
So I have been able to do the upgrade, but I am still wondering why I
got the error in the first place. Any idea why the .pgpass file isn't
working with the pg_upgrade command?
Best regards,
Nick Renders
it's just
that this loop goes slower against real tables than temp tables. For example, I
see similar total memory growth by the time this reaches 100,000 loops for
either temp or non-temp tables, the temp version just reaches that point a lot
more quickly (which makes sense).
Thanks!
Nick
ow any memory growth:
DO $$
DECLARE
i bigint;
BEGIN
CREATE TEMPORARY TABLE pg_temp.foo (id integer);
FOR i IN 1..2 LOOP
TRUNCATE pg_temp.foo;
END LOOP;
END
$$
Any help in determining what's going on here (or if there are other ways to go
about this) would be greatly appreciated!
Thank you!
Nick
On Wed, 2 Dec 2020 at 15:59, Michael Lewis wrote:
> You can not have overlapping partitions that are both attached.
>
Not directly, no. That's why I'm considering the _partition_channel hack.
Why do you want to merge partitions that you are "done with" instead of
> just leaving them partitioned
On Wed, 2 Dec 2020 at 16:07, David G. Johnston
wrote:
> On Mon, Nov 30, 2020 at 8:36 AM Nick Cleaton wrote:
>
>> I want to set up a large table on postgresql 12.4, using declarative
>> partitioning to partition by record creation date. I'd like to have recent
>> re
I want to set up a large table on postgresql 12.4, using declarative
partitioning to partition by record creation date. I'd like to have recent
records in small partitions but old records in a few larger partitions, so
I want merges. The merges should be concurrent, in the sense that they lock
out
Thanks for the reply. Should I post to the separate hackers list, or wait
for someone to chime in here?
FWIW, I am able to access older v12 libpq-dev by using the archive apt
list: https://apt-archive.postgresql.org/ -- so we will do that going
forward until this is resolved.
-Nick
On Wed, Oct
s/apt/ buster-pgdg main 12
However I am still not seeing that version show up. If I remove 'main',
leaving just 12, no versions show up as coming from the postgres repo at
all. Am I missing something else here?
-Nick
On Wed, Oct 7, 2020 at 2:56 PM Adrian Klaver
wrote:
> On 10/7
http://deb.debian.org/debian buster/main amd64 Packages
11.7-0+deb10u1 500
500 http://security.debian.org/debian-security
buster/updates/main amd64 Packagesroot@fb7c949f82a0:/# cat
/etc/apt/sources.list.d/pgdg.listdeb
http://apt.postgresql.org/pub/repos/apt/ buster-pgdg main 12
Thanks,
Nick
On Tue, 19 May 2020 at 22:15, Michael Lewis wrote:
> Increase default_statistics_target, at least on that column, and see if
you get a much much better plan. I don't know where I got this query from
online, but here ya go. I'd be curious how frac_MCV in this changes when
default_statistics_target
On Tue, 19 May 2020 at 21:56, Mohamed Wael Khobalatte
wrote:
> I believe a second ordering, by id desc, will get your query to use the right
> index, and shouldn't be functionally different from what you would expect.
Thanks, that works nicely on our production table, even with much
larger sets
The attached script builds a 10G test table which demonstrates a
problem that we have in production with postgresql 12.3-1.pgdg18.04+1
on ubuntu linux. Indexes:
test_orders_o_date_idx btree(o_date)
test_orders_customer_id_o_date_idx btree(customer_id, o_date)
We query for the most recent orders f
es 9 on macOS 10.12)
and the same issue seems to occur there.
Has anyone noticed something similar with macOS? Or is it just our
setup?
Best regards,
Nick Renders
Hi Tom,
1. we used the EDB installer.
2. turning JIT off did make the problem go away. So I guess this was
causing the Postgres process to crash all along.
Thanks for the help,
Nick
On 24 Feb 2020, at 16:24, Tom Lane wrote:
"Nick Renders" writes:
We have set up a new test e
uence FROM f_gsxws_schedule WHERE UPPER(gwsc_dossier) =
'TEST'
both kill the postgres service.
I will try to free some time next week to install the Apple developer
tools and further analyse the problem.
Best regards,
Nick
On 11 Feb 2020, at 12:32, Nick Renders wrote:
Hi Thomas
Hi Jeremy,
This happend on PostgreSQL v9.6 which crashed 2 weeks ago.
Since then we have upgraded and restored our server, but my example is
from the older, corrupt database.
Nick
On 15 Feb 2020, at 5:30, Jeremy Schneider wrote:
On Feb 14, 2020, at 04:39, Nick Renders wrote:
I get the
IF iCounter % 10 = 0 THEN
RAISE NOTICE '% % records checked', iCounter,
pTableName;
END IF;
iCounter := iCounter+1;
END LOOP;
END;
$f$;
Cheers,
Nick
On 14 Feb 2020, at 16:14, Tom Lane wrote:
&quo
ipt? Or is
there perhaps a better way to check for corrupt records in a database?
Best regards,
Nick Renders
Hi Thomas,
We are setting up a new test environment with 12.1.
Once it is running, I'll try out those commands and get back with the
results.
Thanks,
Nick Renders
On 11 Feb 2020, at 2:51, Thomas Munro wrote:
On Mon, Feb 10, 2020 at 4:35 AM Marc wrote:
We will keep the 12.1 in pla
noticed anything like this before? Any idea how to fix this?
Best regards,
Nick Renders
m here? Is tracking down these corrupt
records and deleting them the best / only solution?
Is there a way to determine of there are issues with new data (after the
crash)?
Any help and advice is very much appreciated.
Thanks,
Nick Renders
On 5 Feb 2020, at 12:51, Alvaro Herrera wrote:
On 2
might have been the reboot, but maybe the reboot was a result
of a Postgres issue.
Is there anything specific I should check in our postgres installation /
database to make sure it is running ok now? Anyway to see what the
consequences were of purging that one pg_clog file?
Best regards,
Nick Renders
is is probably due to you
executing `psql` in terminal without specifying an actual user name.
The way to do this properly would be to execute `psql -U postgres`.
Unfortunately, you've left before I was able to tell you this.
Kind regards,
Nick.
Am 29.01.2019 um 17:39 schrieb Tom Lane:
> "Gunnar \"Nick\" Bluth" writes:
>> Tried
>> SELECT 0x5e73266725;
[...]
> SELECT 0 AS x5e73266725;
>
> and that's the result you got.
Well, yeah, _that_ was pretty obvious. I just didn't e
Hi,
I found this in an SQL-injection attempt today:
union select 0x5e73266725,0x5e73266725[,...],0x5e73266725;
Tried
SELECT 0x5e73266725;
and received:
-[ RECORD 1 ]--
x5e73266725 | 0
That was not what I expected... is this expected/documented behaviour?
Thx in advance!
--
Gunnar "
כתב:
On Mon, 20 Aug 2018 at 09:22, Nick Dro <postgre...@walla.co.il> wrote:
This incorrect.
SELECT position(substring('https://www.webexample.com/s/help?' FROM '/(s|b|t)/') IN 'https://www.webexample.com/s/help?');
Gives 5. It's wrong.On Mon
ning SUBSTRING with position. Something like:SELECT position(substring(URL FROM '/(s|b|t)/') IN URL);Cheers,KenOn Sun, Aug 19, 2018 at 11:27 PM Nick Dro <postgre...@walla.co.il> wrote:Position function allows only string as pattern parameter:
select position(sub-string in string)
Position function allows only string as pattern parameter:
select position(sub-string in string)
If you are looking for more than one sub-string you can't do it with a single call to position.
More info:
https://stackoverflow.com/questions/51925037/how-to-find-position-of-multiple-sub-string-i
On 13 April 2018 at 18:48, Jonathan Morgan
wrote:
> For a system with information stored in a PostgreSQL 9.5 database, in which
> data stored in a table that is deleted must be securely deleted (like shred
> does to files), and where the system is persistent even though any
> particular table like
re or less
coincidental.
Best regards,
--
Gunnar "Nick" Bluth
RHCE/SCLA
Mobil +49 172 8853339
Email: gunnar.bl...@pro-open.de
_
In 1984 mainstream users were choosing VMS over UNIX.
Ten years later they are choosing Windows
n it make sence to have it in it's base code - ready for use rather than ask each one to implment his own.
ב דצמ׳ 19, 2017 17:51, Melvin Davidson כתב:
On Tue, Dec 19, 2017 at 4:54 AM, Pavel Stehule <pavel.steh...@gmail.com > wrote:
2017-12-19 10:13 GMT+01:00 Nick Dro <postg
postgresql should have build in function for percentage calculation it doesn't have to me the exact example I gave. Any thing will be better than none.
ב דצמ׳ 18, 2017 18:28, Michael Nolan כתב:
On Mon, Dec 18, 2017 at 6:23 AM, Nick Dro <postgre...@walla.co.il > wrote:
Hi,
Why
very basic mathematical operations.
Can you give a good reason why absolute value has a build in function while percentage is not?
ב דצמ׳ 18, 2017 17:44, hubert depesz lubaczewski כתב:On Mon, Dec 18, 2017 at 02:23:38PM +0200, Nick Dro wrote:
>Hi,
>Why PostgreSQL doesn't have build-in
Hi,
Why PostgreSQL doesn't have build-in function to calculate percentage? somthing like percent(number,%
for example:
select percent(100,1) will calculate 1% of 100 = 1
select percent(25,20) will calculate 20% of 25 = 5
Seems like a nice addition to the math functions list:
https://www.postgresq
59 matches
Mail list logo
