Hi Andres-
Thanks for the reply, answers below.
On Tue, Mar 17, 2020 at 8:19 PM Andres Freund wrote:
>
> Hi,
>
> On 2020-03-17 17:18:57 -0500, Justin King wrote:
> > As you can see in this table, there are only ~80K rows, but billions
> > of updates. What we have observ
On Wed, Mar 18, 2020 at 10:13 AM Adrian Klaver
wrote:
>
> On 3/18/20 6:57 AM, Justin King wrote:
> Please reply to list also
> Ccing list
>
>
> >>> Here are the settings, these are the only ones that are not set to
> >>> default with the exception
On Wed, Mar 18, 2020 at 1:40 PM Michael Lewis wrote:
>
> Do you have default fillfactor set on this table? If not, I would wonder if
> reducing it to 50% or even 20% would allow many more HOT updates that would
> reduce bloat.
I don't believe we have a default fillfactor, but I'm still trying t
On Thu, Mar 19, 2020 at 11:02 AM Michael Lewis wrote:
>
> On Thu, Mar 19, 2020 at 9:31 AM Justin King wrote:
>>
>> On Wed, Mar 18, 2020 at 1:40 PM Michael Lewis wrote:
>> >
>> > Do you have default fillfactor set on this table? If not, I would wonder
&
On Thu, Mar 19, 2020 at 5:35 PM Andres Freund wrote:
>
> Hi,
>
> On 2020-03-19 10:23:48 -0500, Justin King wrote:
> > > From a single stats snapshot we can't actually understand the actual xid
> > > consumption - is it actually the xid usage that triggers the
On Thu, Mar 19, 2020 at 6:56 PM Andres Freund wrote:
>
> Hi,
>
> On 2020-03-19 18:07:14 -0500, Justin King wrote:
> > On Thu, Mar 19, 2020 at 5:35 PM Andres Freund wrote:
> > >
> > > Hi,
> > >
> > > On 2020-03-19 10:23:48 -0500, Justin King
On Mon, Mar 23, 2020 at 3:00 PM Andres Freund wrote:
>
> Hi,
>
> On 2020-03-23 20:47:25 +0100, Julien Rouhaud wrote:
> > > - relfrozenxid, age(relfrozenxid) for the oldest table in the oldest
> > > database
> > > SELECT oid::regclass, age(relfrozenxid), relfrozenxid FROM pg_class
> > > WHERE r
On Mon, Mar 23, 2020 at 4:31 PM Justin King wrote:
>
> On Mon, Mar 23, 2020 at 3:00 PM Andres Freund wrote:
> >
> > Hi,
> >
> > On 2020-03-23 20:47:25 +0100, Julien Rouhaud wrote:
> > > > - relfrozenxid, age(relfrozenxid) for the oldest table in the old
) DESC
LIMIT 3;
slot_name | xmin | age | catalog_xmin | age
---+--+-+--+-
(0 rows)
postgres=# SELECT gid, database, transaction FROM pg_prepared_xacts
ORDER BY age(transaction) LIMIT 3;
gid | database | transaction
-+--+-
(0 rows)
Let me know if there's anyt
On Wed, Mar 25, 2020 at 8:43 PM Michael Paquier wrote:
>
> On Wed, Mar 25, 2020 at 10:39:17AM -0500, Justin King wrote:
> > This started happening again. DEBUG1 is enabled:
>
> Thanks for enabling DEBUG1 logs while this happened.
>
> > Mar 25 14:48:26 cowtn postgres[3
On Fri, Mar 27, 2020 at 12:12 AM Michael Paquier wrote:
>
> On Thu, Mar 26, 2020 at 09:46:47AM -0500, Justin King wrote:
> > Nope, it was just these tables that were looping over and over while
> > nothing else was getting autovac'd. I'm happy to share the full log
&
DEBUG: shmem_exit(1):
6 on_shmem_exit callbacks to make", 140, MSG_NOSIGNAL, NULL, 0) = 140
sendto(4, "\x58\x00\x00\x00\x04", 5, MSG_NOSIGNAL,
NULL, 0) = 5
Any suggestions?
Thanks-
Justin
On Thu, Apr 23, 2020 at 12:47 PM Tom Lane wrote:
>
> Justin King writes:
> > We've seen unexpected termination of the WAL receiver process. This
> > stops streaming replication, but the replica stays available --
> > restarting the server resumes streaming
seemingly random times. Also, just to clarify, this will only happen
on a single replica at a time.
On Thu, Apr 23, 2020 at 2:46 PM Justin King wrote:
>
> On Thu, Apr 23, 2020 at 12:47 PM Tom Lane wrote:
> >
> > Justin King writes:
> > > We've seen unexpect
On Thu, Apr 23, 2020 at 3:06 PM Tom Lane wrote:
>
> Justin King writes:
> > I assume it would be related to the following:
> > LOG: incorrect resource manager data checksum in record at 2D6/C259AB90
> > since the walreceiver terminates just after this - but I'm un
ystem in common -- particularly ZFS
(or btrfs, in the bottom case). Is there anything more we can do here
to help narrow down this issue? I'm happy to help, but I honestly
wouldn't even know where to begin.
Thanks-
Justin King
flightaware.com
On Thu, Apr 23, 2020 at 4:40 PM Justin King
org/message-id/20200427181034.ga28...@telsasoft.com
|... 1) create an child table: CREATE TABLE x_child() INHERITS(x)
|and, 2) change the query to use "select from ONLY".
|
|(1) allows the planner to believe that the table really is empty, a conclusion
|it otherwise avoids and (2) avoids decending into the child (for which the
|planner would likewise avoid the conclusion that it's actually empty).
--
Justin
cleaner output.
and:
|commit c8961bf1ce0b51019db31c5572dac18b664e02f1
|Author: Bruce Momjian
|Date: Fri Aug 4 18:53:46 2006 +
|
|Improve logging of protocol-level prepared statements.
Justin
8gb e grows
> until use them all. When all memory is in use then it starts to swap. When
> all swap is allocated then it gets the "out of memory" and stops
> completelly.
> on: https://drive.google.com/open?id=18zIvkV3ew4aZ1_cxI-EmIPVql7ydvEwi*
It says "Access Denied", perhaps you could send a link to
https://explain.depesz.com/ ?
Justin
On Fri, Feb 08, 2019 at 07:29:53AM -0600, Justin Pryzby wrote:
> A couple months ago, I implemented prepared statements for PyGreSQL. While
> updating our application in advance of their release with that feature, I
> noticed that our query logs were several times larger.
Previousl
ttps://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=b23852766
Justin
Moving to -general list (-hackers is for development topics like proposed
patches and patch reviews and beta testing and crash reports).
On Thu, Feb 28, 2019 at 10:13:58AM -0800, Perumal Raj wrote:
> could not load library "$libdir/pg_reorg":
> ERROR: could not access file "$libdir/pg_reorg": No
the upgrade, you can CREATE EXTENSION pg_repack, which is a fork of
pg_reorg, which is itself no longer maintained.
Justin
t.
But was probably installed by running some SQL script.
It tentatively sounds safe to me to drop, but you should take a backup and
inspect and double check your pg_dump output and output of "begin; drop schema
pgreorg cascade".
Justin
On Tue, Mar 05, 2019 at 08:09:12AM -0800, Perumal Raj wrote:
> Thanks Sergei/Justin for the continues update.
>
> So reorg Schema might be created as part of some scripts prior to 9.2
> Version ?
I'm guessing they were probably created in 9.2.
> These are the functions in
?
You probably have an old DB directory laying around which is (at least
partially) hardlinks. You should remove it .. but be careful to remove the
correct dir. My scripts always rename the old dir before running pg_upgrade,
so it's less scary to rm -fr it later.
Justin
ERE log_time>'2019-04-10 10:50' AND
message~'^duration:') SELECT date_trunc('minute',log_time)log_time, dur,
error_severity, session_id, user_name, database, left(message,99),
left(query,99)
FROM x WHERE dur> AND (application_name!='psql' OR user_name='postgres') ;
|postgres=# explain analyze SELECT date_trunc('minute',log_time)log_time, dur,
error_severity, session_id, user_name, database, left(message,99),
left(query,99)
FROM (SELECT *,regexp_replace(message, '^duration: ([.0-9]+) ms.*',
'\1')::float AS dur FROM postgres_log_2019_04_10_1000 WHERE
log_time>'2019-04-10 10:50' AND message~'^duration:' OFFSET 0)x WHERE
dur> AND (application_name!='psql' OR user_name='postgres') ;
Thanks in advance for any advice.
Justin
Is it still impossible to distinguish whether a row was inserted vs updated ?
The latest I can see is here:
https://wiki.postgresql.org/wiki/UPSERT#RETURNING_behavior
..but I'm hopeful that the 4 year old wiki page is out of date.
Justin
On Tue, May 21, 2019 at 06:57:36PM -0700, Adrian Klaver wrote:
> On 5/21/19 6:34 PM, Justin Pryzby wrote:
> >Is it still impossible to distinguish whether a row was inserted vs updated ?
>
> You will need to be more specific.
Sorry, I mean with UPSERT / "INSERT .. ON CONFLI
r version is already tracked somewhere as well, that
would be extremely useful for my use case.
Otherwise, I'll have to start manually adding info to track it.
Regards and best wishes,
Justin Clift
On 2023-08-19 14:10, David G. Johnston wrote:
On Fri, Aug 18, 2023 at 6:36 PM Justin Clift
wrote:
If the minor version is already tracked somewhere as well, that
would be extremely useful for my use case.
The data directory doesn't have a concept of "minor version". Onl
On 2023-08-19 19:14, Peter J. Holzer wrote:
On 2023-08-19 14:22:25 +1000, Justin Clift wrote:
Thanks, that's what I figured. I'll have to keep state in a
PG_VERSION_MINOR
there or something. :)
Wouldn't it be better to ask whatever system you use to install the
software
using PostgreSQL, but are instead
using a special proprietary spin-off called Greenplum.
If that's the case, then you'll need to have a chat with the Greenplum
support people. They'll know their product better than we do. :)
Regards and best wishes,
Justin Clift
*sure* it's PostgreSQL 15.4, and not PostgreSQL 12.4?
Asking because I'm not seeing version PG 15.4 in the list here, though
PG 12.4 and 16 are:
http://hpux.connect.org.uk/hppd/cgi-bin/search?term=postgresql
Regards and best wishes,
Justin Clift
On 2023-10-21 21:13, Dave Cramer wrote:
On Sat, 21 Oct 2023 at 05:50, Justin Clift
wrote:
On 2023-10-19 04:45, Abelardo Erazo Lopez wrote:
> Hi, Everyone
>
> I have an Oracle database Oracle 19c and I need to access a PostgreSQL
> database 15.4 that resides on a different server
https://github.com/openzfs/zfs/discussions/14793
Note - that's not PostgreSQL specific or anything, but more of a
"weird stuff showing up with NVMe drives" thing.
Regards and best wishes,
Justin Clift
that can show a log of any recent weirdness that occurred at a
hardware level.
If yours can, take a look for things like ECC errors or any other
strange stuff. :)
Regards and best wishes,
Justin Clift
On 2023-11-09 11:41, yangsr3411 wrote:
Finally, we used the Windows tool Gflags.exe and found that other
software terminated the postgres process.
Out of curiosity, what was the other software? :)
Regards and best wishes,
Justin Clift
re aren't more,
similar complaints about this. It's as Peter said: it (sometimes)
causes systemd to actively *stop* the cluster after OOM, when it
would've come back online on its own if the init (supervisor) process
didn't interfere.
My solution was to set:
/usr/lib/systemd/system/postgresql@.service OOMPolicy=continue
I suggest that the default unit files should do likewise.
--
Justin
ot;myimage:latest",
which you can then use as you need later on.
Does that make sense?
Regards and best wishes,
Justin Clift
le-to-postgresql-migration-guide-tutorial-move-convert-database-oracle-alternative
Regards and best wishes,
Justin Clift
pure guess work though. :)
Regards and best wishes,
Justin Clift
As always though, make sure you have a backup (that's known to work)
before
you try it all out though. :)
+ Justin
t-ize this. Stay tuned
Hopefully it get approved. More battle tested queue systems are
welcome,
especially those that have been used at non-trivial scales. :D
+ Justin
27;t seem to be optimised for loading into a database. (?)
It kind of looks like they'd be stored into individual records,
which probably means they'd be getting imported as individual
INSERT statements rather than something that's optimised for
bulk loading. :(
Regards and best wishes,
Justin Clift
ace (depends on the storage you're
using),
you could potentially load things from that backup / snapshot (etc)
instead
of having to do the import all over again each time.
Regards and best wishes,
Justin Clift
n" test of all the
things (memory, hard disks/ssds, cpu, gpu, etc) just to make sure
everything is ok before you start using it for important stuff.
Regards and best wishes,
Justin Clift
ght person.
?
Regards and best wishes,
Justin Clift
On 2024-05-02 13:24, Bagesh kamar singh wrote:
Recently we migrated our postgreSQL single server to flexi server.
Hmmm, what's "Flexi server"?
Doing a quick online search just now isn't showing things that seem
to be PostgreSQL related.
Regards and best wishes,
Justin Clift
cally and factually correct. Use of AI should be
used for minor editing, not primary generation"
Sounds pretty sensible. :)
+ Justin
Hello,
I have an issue that on the surface seems orthogonal to existing functionality.
I'm trying to dynamically update validity ranges as new s replace old
s.
In a nutshell the problem looks like this:
psqlprompt=# select * from rangetest;
id | rangecol
+-
ng commit as at first I thought it might
be related to Memoize. It does not seem to be.
As a general thought, seeing that this might be an actual problem
should some kind of automated testing be added that checks for
performance regressions like this?
Regards and best wishes,
Justin Clift
On 2024-08-27 20:14, David Rowley wrote:
On Tue, 27 Aug 2024 at 18:00, Justin Clift
wrote:
As a general thought, seeing that this might be an actual problem
should some kind of automated testing be added that checks for
performance regressions like this?
We normally try to catch these sorts
sions and stuff like that.
Thoughts?
Regards and best wishes,
Justin Clift
e new locale data. Therefore, caution will be necessary when
upgrading.
> Is PostgreSQL 11 compatible with RHEL 8.4
How did you install postgres ?
Compiled from source ?
Using RHEL packages ?
Using PGDG packages ?
PDDG has pacakges for PG11/RH8
https://yum.postgresql.org/rpmchart/#pg11
--
Justin
e from postgres 9.6 to 11;
You may need to install updated PGDG packages for the RH8.
How are you planning to upgrade postgres ?
Using pg_upgrade, or pg_dump, or ??
> Postgres is installed using PGDG packages.
>
> On Thu, Aug 26, 2021 at 1:15 AM Justin Pryzby wrote:
>
> > On We
day's pg_upgrade;
- I have a script saving something from pg_buffercache, but it doesn't appear
to be running during this last incident;
- I'm planning do disable sync seqscan for the night (although as I understand
that may not matter (?))
- this instance has clients connecting to ~10 DBs;
Thanks in advance
Justin
On Tue, Nov 21, 2017 at 03:45:58PM -0800, Andres Freund wrote:
> On 2017-11-21 18:21:16 -0500, Tom Lane wrote:
> > Justin Pryzby writes:
> > > As $subject: backends are stuck in startup for minutes at a time. I
> > > didn't
> > > strace this time, but
On Tue, Nov 21, 2017 at 03:40:27PM -0800, Andres Freund wrote:
> Hi,
>
> On 2017-11-21 17:09:26 -0600, Justin Pryzby wrote:
> > I'm sorry to report this previously reported problem is happening again,
> > starting shortly after pg_upgrading a customer to PG10.1 from 9
On Tue, Nov 21, 2017 at 03:40:27PM -0800, Andres Freund wrote:
> Hi,
>
> On 2017-11-21 17:09:26 -0600, Justin Pryzby wrote:
> > I'm sorry to report this previously reported problem is happening again,
> > starting shortly after pg_upgrading a customer to PG10.1 from 9
On Wed, Nov 22, 2017 at 01:27:12PM -0500, Tom Lane wrote:
> Justin Pryzby writes:
> [ in an earlier post: ]
> > BTW this is a VM run on a hypervisor managed by our customer:
> > DMI: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform,
> > BIOS 6.00 06/
On Wed, Nov 22, 2017 at 01:27:12PM -0500, Tom Lane wrote:
> Justin Pryzby writes:
> > On Tue, Nov 21, 2017 at 03:40:27PM -0800, Andres Freund wrote:
> >> Could you try stracing next time?
>
> > I straced all the "startup" PIDs, which were all in futex, witho
On Wed, Nov 22, 2017 at 07:43:50PM -0500, Tom Lane wrote:
> Justin Pryzby writes:
> > For starters, I found that PID 27427 has:
>
> > (gdb) p proc->lwWaiting
> > $1 = 0 '\000'
> > (gdb) p proc->lwWaitMode
> > $2 = 1 '\001'
>
>
On Sat, Nov 25, 2017 at 05:45:59PM -0500, Tom Lane wrote:
> Justin Pryzby writes:
> > We never had any issue during the ~2 years running PG96 on this VM, until
> > upgrading Monday to PG10.1, and we've now hit it 5+ times.
>
> > BTW this is a VM run on a hyper
Thank you very much. I had a stale replication slot. I removed it and the
logs were cleaned up immediately.
--Justin
On Thu, Apr 10, 2025 at 8:48 AM Laurenz Albe
wrote:
> On Thu, 2025-04-10 at 08:28 -0400, Justin Swanhart wrote:
> > I have the following in my postgresql.conf fo
& mv
%p /var/lib/postgresql/prod_archive_logs/%f'
When I did this the archives were moved away to the archive directory but
when I tried to set up replication the server could not find the archived
log to replicate from so I changed it to "cp" and now have this problem.
What am I missing?
Regards,
--Justin
c in plancache.c doesn't make much sense.
Justin Blank
:)
Regards and best wishes,
Justin Clift
Original Message
Subject: Schemaverse
Date: 2025-04-21 13:01
From: Joshua McDougall
To: jus...@postgresql.org
Hi Justin,
To answer your question, Schemaverse doesn’t take massive power to host.
It needs a database and a small server fo
seful for larger databases, and for situations where you don't
have
much space.
BUT, you *do* have backups don't you?
Because stuff *can* go wrong, even though it's not common. ;)
Regards and best wishes,
Justin Clift
On 2025-05-06 09:15, Merlin Moncure wrote:
On Thu, May 1, 2025 at 5:23 PM Justin Clift
wrote:
Hi all,
The PostgreSQL game "Schemaverse" was removed from the PostgreSQL
website's
links a few months ago because it no longer had hosting.
Does anyone around have spare server/vm
gcp; I'll set
something up. Out of town until late next week but I'll circle back
then.
Have you had a chance to investigate? :)
Regards and best wishes,
Justin Clift
olders the actual picture of our system.
I'd be grateful for any hints !
Maybe Corteza?
https://cortezaproject.org
We do stuff with it at my work, and it's pretty decent.
Takes some time and effort to set up though, but is very capable
once that's done.
Regards and best wishes,
Justin Clift
101 - 172 of 172 matches
Mail list logo
