I've got two Postgres 13 databases on AWS RDS.
* One is a master, the other a slave using logical replication.
* Replication has fallen behind by about 350Gb.
* The slave was maxed out in terms of CPU for the past four days because of
some jobs that were ongoing so I'm not sure what l
E.
Regards
Mike
On Wed, 7 Aug 2024 at 18:09, David Rowley wrote:
>
> On Wed, 7 Aug 2024 at 19:20, Michael Harris wrote:
> > I found that running an ANALYZE specifying only those 4 columns only took
> > 5 minutes, compared to the 30 minutes for the whole table.
> >
> > T
Many thanks David for the comprehensive response.
> I think the complaint was about no autovacuum on the partitioned
> table, not the partitions.
Yes, exactly.
One other piece of information: these tables contain a lot of columns, of which
only 4 are normally used for WHERE clauses or joins. The
Hello Experts,
Our application has a database with a large number of partitioned tables
used to store time series data.
It is partitioned by time: new data is populated into the current
partition, old partitions eventually get dropped, and the partitions in
between are largely static.
I had not
On Thu, Jul 18, 2024 at 4:38 AM sivapostg...@yahoo.com
wrote:
>
> Hello,
> PG V11
>
> Select count(*) from table1
> Returns 10456432
>
> Select field1, field2 from table1 where field3> '2024-07-18 12:00:00'
> Times out
>
> The above query was working fine for the past 2 years.
>
> Backup was taken
On Sun, Jul 7, 2024 at 4:13 AM Pavel Stehule wrote:
>
> but looks so there are false alarms related to using an alias. It is
> interesting so I have not any report about this issue, so probably using
> aliases is not too common today.
I'm not sure why there's a warning about using an alias. 43.
In the following short code, the out parameter d3 is also declared, so
its value will be null in the output.
create or replace function public.test_function(in varchar, in char, in date, ou
t d1 text, out d2 integer, out d3 char, out d4 date )
stable as $$
DECLARE
wk_intxt alias for $1;
wk
I don't have any direct experience with Yugabyte (the databases I work
with are way too small to be on Yugabyte) but my older son does work
for them as an SRE, sometimes remotely when he's visiting us, so we've
talked about it a bit. (It's actually the first time in 20 years I've
had much of a clu
d a default =X/rolename.
Examining \ddp and its underlying quuery, I see that view column
pg_default_acl gets a new row with defaclacl populated after the ALTER DEFAULT
PRIVILEGES.
Thanks very much for your guidance, I am on track now.
Mike Tefft
From: Tom Lane
Sent: Friday, July 5, 2024 2:2
be checking
instead?
Thanks,
Mike Tefft
From: Tom Lane
Sent: Friday, July 5, 2024 10:51 AM
To: Tefft, Michael J
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Removing the default grant of EXECUTE on functions/procedures to
PUBLIC
"Tefft, Michael J" writes: > I am trying t
I am trying to remove the default grant of EXECUTE on all functions/procedures
to PUBLIC.
>From my reading, there is no straightforward way to do this. For example,
ALTER DEFAULT PRIVILEGES REVOKE EXECUTE ON FUNCTIONS FROM PUBLIC;
Does not apply this across the entire cluster (or database) but onl
uld
begin some sort of investigation, for example, to know what is
happening to your system and figure out if there is even something
wrong going on.
Thanks,
--
Michael
signature.asc
Description: PGP signature
d for it today by me down to v15. This will
show up in the next round of minor releases.
--
Michael
signature.asc
Description: PGP signature
My production server has a materialized view that is refreshed from a
mysql_fdw several times a day.
What I'd like to be able to do is refresh the materialized view on the
testbed server from the one on the production server so that they are
the same. (Refreshing it from the MySQL server will res
OREIGN KEY (par_file_id) REFERENCES
par_log_file(par_file_id);
Version Postgres 13.13
Any help would be appreciated/
--
Michael Corey
two .signal files when promotion is achieved would be
a problem to me because we'd reenter recovery again at a follow-up
startup. ArchiveRecoveryRequested should be set if there was either
recovery.signal or standby.signal found at startup, meaning that we
should have a TLI jump at promotion
where
schemaname='sss' and tablename='xxx' and attname = ‘col1’;
So setting n_distinct on the column at the parent/partitioned-table level is
not relevant for this.
Thanks again.
Mike Tefft
From: Greg Sabino Mullane
Sent: Monday, March 11, 2024 12:23 PM
To: Laurenz Albe
negative, but none carry the value I attempted to
set
Thanks,
Mike Tefft
-Original Message-
From: Laurenz Albe
Sent: Monday, March 11, 2024 9:21 AM
To: Tefft, Michael J ;
pgsql-general@lists.postgresql.org
Subject: Re: alter table xxx alter column yyy set (n_distinct= );
On Mon
I have been struggling to set n_distinct on a few table columns, and confirm
that my changes have actually been accepted.
I have a 400-million row table with 81 partitions. PostgreSQL version is 14.11.
Column p_id has 13 million distinct values but pg_stats says n_distinct is only
82k.
Column pi
sync?
On Fri, Feb 16, 2024 at 11:35 AM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Fri, Feb 16, 2024 at 9:24 AM Michael Corey <
> michael.corey...@nielsen.com> wrote:
>
>> If I run these two statements I get an error
>> ERROR: relation "part_t
ations of this ALTER TABLE statement and none seem
to work. What is the proper way to reattach the identity and the sequence
bearing in mind that I will load the new table with the data from the old
table?
--
Michael Corey
RangeVar, so there is no "easy" way to
tackle that :/
--
Michael
signature.asc
Description: PGP signature
Followup: The problem turned out to be a field in the mysql server
that was not size-limited to 255 characters and had several rows with
as many as 299 characters in them. Apparently when using an FDW and
materialized view in postgresql 10.4, field size limits aren't
checked, because a query on t
On Thu, Jan 25, 2024 at 3:38 PM Tom Lane wrote:
>
> Michael Nolan writes:
> > On the 10.4 server this materialized view works, but on the 16.1
> > server it fails:
>
> > uscf=# refresh materialized view uscf_vip;
> > refresh materialized view uscf_vip;
&
I'm in the process of updating a server from postgresql 10.4 on Centos
7 to 16.1 on AlmaLInux 9, and am reminded of the old line about when
you're up to your necks in alligators, it is difficult to remember
that your goal was to drain the swamp.
We have several materialized views that are refreshe
No, it wasn't there, because I hadn't included --with-openssl in the
configure. Looking at my history, I had done that once earlier but
dropped it for the reason noted below.
Including --with-openssl does include the crypto library, but if I
don't do a 'make clean' before doing a make, I get erro
Sorry, I meant 'make check'. :sigh:
Writing or debugging makefiles is something I haven't done much of,
but as best I can figure out the problem is that the libcrypto.so file
isn't being linked in, though this line in the Makefile in pgcrypto
seems to say should be:
SHLIB_LINK += $(filter -lcrypto -lz, $(LIBS))
I'm guessing it is s
On Thu, Jan 18, 2024 at 9:51 AM Tom Lane wrote:
>
> Looks like we have aarch64 and ppc64 machines running Alma 8 and 9.
> No x86 though, which might matter for such a low-level failure
> as this.
So I guess that'll be on the list to add to the build farm at some
point? (My Xanthian 'talent' of f
On Thu, Jan 18, 2024 at 5:03 AM Daniel Gustafsson wrote:
>
> > On 18 Jan 2024, at 00:59, Michael Nolan wrote:
> > On Wed, Jan 17, 2024 at 5:32 PM Daniel Gustafsson wrote:
> >>
>
> That's surprising, I expected that it would require the legacy provider be
On Wed, Jan 17, 2024 at 5:32 PM Daniel Gustafsson wrote:
>
> > On 18 Jan 2024, at 00:24, Michael Nolan wrote:
> >
> > Sorry for the delay in responding, network issues kept me offline for
> > several days.
> >
> > These are the openssl packages inst
Sorry for the delay in responding, network issues kept me offline for
several days.
These are the openssl packages installed from the Almalinux 9 repositories:
apr-util-openssl.x86_64 1.6.1-23.el9 @appstream
openssl.x86_641:3.0.7-24.el9
This is on AlmaLinux 9.3, installing postgresql from source code.
In PG 16.1 when I try to install pgcrypto, the modules compile but I
get this error when running checks:
CREATE EXTENSION pgcrypto;
+ERROR: could not load library
"/home/postgres/src/postgresql-16.1/tmp_install/usr/local/pgsql/li
har(now() at time zone 'Europe/Amsterdam', '-MM-DD
HH24:MI:SS.US0 TZH:TZM');
to_char
----
2024-01-11 16:24:52.8736860 +00:00
(1 row)
At least it seems to do what you need.
Regards,
Michael
>
> I'm dealing with a data virt
tails, and work on fixing the issue.
--
Michael
signature.asc
Description: PGP signature
I'm trying to install mysql_fdw_16 and it requires the mariadb-devel module.
There is no mariadb-devel module for Almalinux 9. There is a
MariaDB-devel module, but when I install it, the install for
mysql_fdw_16 still tells me that there is no mariadb-devel module
available.
How do I work around
have here is that we've lost track of the
patch proposed, so I have added a CF entry for now:
https://commitfest.postgresql.org/46/4720/
--
Michael
signature.asc
Description: PGP signature
plicated to the standby.
- Promote the standby.
- Enable checksums on the previous primary.
- Start the previous primary to be a standby of the node you failed
over to.
--
Michael
signature.asc
Description: PGP signature
or older snapshots held by concurrent sessions when the
index build is finished and when the index built gets validated.
--
Michael
signature.asc
Description: PGP signature
Sorry for the top posting, I forget that Gmail does that by default.
Mike Nolan
To add to what Steve has said, see if you can find a room with
equipment similar to what you'll be using for the actual presentation
to practice in. Put up your most complex slide, then take a seat in
the back of the room and imagine what it'll look like with a room full
of people in front of you.
I'm not clear which rows are duplicates.
It looks like limb_id, branch_id and twig_id make up a unique key.
If there was a row (2, 2, 7,103.7) would it be a duplicate of rows
(1,1,2,103.7) and (1,1,3,103.7)?
--
MIke Nolan
y to them. I have an example of this kind of
idea in one of my plugin modules here:
https://github.com/michaelpq/pg_plugins/tree/main/jsonlog
--
Michael
signature.asc
Description: PGP signature
les, but should I take an exclusive lock on the table,
> switch it to unlogged,
> rewrite, and switch it back to logged?
Switching a table back to be logged requires all its 8k blocks to be
WAL-logged, so that would be roughly the same as a plain UPDATE.
--
Michael
signature.asc
Description: PGP signature
lation if you are too aggressive with the updates. You
could do that in periodic steps, as well.
--
Michael
signature.asc
Description: PGP signature
t sure that this is the correct path to do
so or that in some cases forcing the hand of the user was incorrect.
It was also creating a penalty in some of the hot loops of area:
commit: dbab0c07e5ba1f19a991da2d72972a8fe9a41bda
committer: Michael Paquier
date: Mon, 14 Jun 2021 09:25:50 +0900
Remove force
something
changed in the underlying Postgres build.
On Wed, Sep 20, 2023 at 7:11 PM Erik Wienhold wrote:
> On 2023-09-20 17:53 -0400, Michael Corey wrote:
> > To make matters even more strange. I checked the permissions of
> > rds_superuser in 15 and 14
> >
> >
,
*pg_write_all_data*, rds_password, rds_replication TO rds_superuser WITH
ADMIN OPTION;
AWS added these permissions, but based on what they do you would think this
would allow the SELECTs in 15.
On Wed, Sep 20, 2023 at 4:40 PM Erik Wienhold wrote:
> On 2023-09-20 15:19 -0400, Michael Corey wr
hema?
>> Because it must inherit SELECT on ref_media_code on 14.3. It can't be
>> from object_creator because that role also gets newly created.
>>
>
> Your description also suggests that maybe the v14 instance has altered
> default privileges setup that maybe the v15 doesn't have.
>
> David J.
>
>
--
Michael Corey
original 14 server and made two copies. I kept one as 14 and upgraded
the other to 15. Lastly, I created the test case.
On Wed, Sep 20, 2023 at 3:07 PM Erik Wienhold wrote:
> On 2023-09-20 13:17 -0400, Michael Corey wrote:
> > PG 14 Server
> > psql (14.2, server 14.3)
> > You
atabases and received different results.
On Wed, Sep 20, 2023 at 12:33 PM Erik Wienhold wrote:
> On 2023-09-20 09:15 -0400, Michael Corey wrote:
> > Thanks for responding. All of the DDL is just the setup for the test
> > case. I ran those steps in both databases to setup the exac
sten_schema, but in 15.3 I am unable due to a permission issue.
On Tue, Sep 19, 2023 at 8:17 PM Erik Wienhold wrote:
> On 2023-09-19 15:09 -0400, Michael Corey wrote:
> > We are experiencing different functionality once we upgraded from
> Postgres
> > 14.3 to Postgres 15.3.
> >
We are experiencing different functionality once we upgraded from Postgres
14.3 to Postgres 15.3.
Below is a test case that we created which shows a schema user who has a
VIEW that accesses a table in another schema. In 14.3 the schema user is
able to create the VIEW against the other schema's ta
, I would agree with you that it is not especially useful to keep
it around once the cluster has been recovered from a base backup. It
would actually lead to various errors if attempting to run
pg_verifybackup on its data folder, for instance.
--
Michael
signature.asc
Description: PGP signature
more details about what's happening. For example, what do the
logs of the standby tell you? Are you sure that the reload was done
on the correct node? Did you check with a SHOW command that the new
value is reflected on your standby to what you want it to be?
--
Michael
signature.asc
Description: PGP signature
om here on would be
* persisted. To avoid that, fsync the entire data directory.
--
Michael
signature.asc
Description: PGP signature
It's not just Ruby, dumb databases are preferred in projects like
WordPress, Drupal and Joomla, too.
Now, if it's because they're used to using MySQL, well maybe that's
not so hard to understand. :-)
On Mon, Jun 26, 2023 at 8:05 PM Guyren Howe wrote:
>
> This is a reasonable answer, but I want
s all the
development discussions are done by email on the mailing list
pgsql-hackers, mostly.
--
Michael
signature.asc
Description: PGP signature
speaks
directly the protocol and because it has no dependency to libpq. Are
there any specific failures you are seeing in the PostgreSQL backend
that you find confusing?
--
Michael
signature.asc
Description: PGP signature
team implement them.
>
> Operationally much simpler to have a listener handle that.
>
> -- Born in Arizona, moved to Babylonia.
Hello Ron,
I have to agree with you there as well. The workflow you have to go through is
also often a time issue.
There are many places that have to agree and then application owners still have
to provide justifications.
At the same time, we have to be flexible and fast and allocate the resources
well at any time and provide the application with the maximum possible
performance.
Regards
Michael
32 ─┐ ┌──┬──> PG_Cluster1@localhost:5433
>> ─> pgs2.server.net:5432 ─┤ │ ├──> PG_Cluster2@localhost:5434
>> ─> pgs3.server.net:5432 ─┼─>─┤ 192.168.0.1:5432 ├──>
>> PG_Cluster3@localhost:5435
>> ─> pgs4.server.net:5432 ─┤ │ ├──> PG_Cluster4
Can you use a CASE statement? The real issue with date conversion is
not knowing if a value of 02-03-2023 is mm-dd- or dd-mm-.
On Wed, Jun 14, 2023 at 11:42 AM Marc Millas wrote:
>
> Hi,
>
> I would like to load data from a file via file_fdw or COPY.. its a postgres
> 14 cluster
>
> but
You're gonna lock yourself into SOMETHING, that's why there are still
thousands of COBOL programs still being maintained.
Mike Nolan
On Fri, Jun 9, 2023 at 3:39 PM Ron wrote:
>
> You can be sure that banks and academic research projects have different
> needs. Heck, your University's class sch
Clearly I'm a 73 year old dinosaur, because I believe in having the
business logic in the database wherever possible. But the development
projects I've been around lately aren't using triggers at all. (And
it should not surprise anyone, certainly not me, that consistency of
data enforcement is an
Please, use the following runbook.
1. Disable the subscription to pg10.
2. Disable Application Users on Publisher.
3. Drop all replication slots on Publisher (The upgrade can not be executed
if there are any replication slots)
4. Run RDS's upgrade (which runs pg_upgrade).
5. Recreate replication sl
we, err, revisit the choice of making WAL_LOG
the default strategy even for this set of minor releases? FWIW, I've
mentioned that this choice was too aggressive in the thread of
8a86618..
--
Michael
signature.asc
Description: PGP signature
LE, or is that 15.2-ish without fa5dd46?
One thing I was wondering about to improve the odds of the hits is to
be more aggressive with the number of relations created at once, so as
we are much more aggressive with the number of pages extended in
pg_class from the origin database.
--
Michael
sign
Okay - that worked.
How did you know that would work? That's incredible.
On Sun, May 7, 2023 at 4:25 PM Tom Lane wrote:
> "Michael P. McDonnell" writes:
> > I have 2 stored procedures that need to run back to back. It could
> > convert to a single one - but
in a way similar to Evgeny.
--
Michael
signature.asc
Description: PGP signature
ll these
steps are stable in the backend, at least here. Or do we have some
low-hanging fruit with the WAL_LOG strategy? That could always be
possible, of course, but that looks like the same issue to me, just
with a different symptom showing up.
--
Michael
signature.asc
Description: PGP signature
Hey team -
I have 2 stored procedures that need to run back to back. It could
convert to a single one - but it's easier from a maintenance perspective to
keep them separated.
The first procedure effectively is
INSERT INTO table_b () SELECT FROM _table_a_;
COMMIT;
Total execution time - about
Hi Michael,
Are pthread_* functions really such an improvement over clone? Does it make
an 'freely passing around' of PGresult objects possible? Like it matters,
process or thread.
We were talking about the documentation and this 'freely passing around'
PGresult object. I ju
anytime PG or
anything else Linux based says thread they’re talking about a POSIX Thread
environment.
On Wed, May 3, 2023 at 05:12 Michael J. Baars <
mjbaars1977.pgsql.hack...@gmail.com> wrote:
> Hi Peter,
>
> The shared common address space is controlled by the clone(2) CLONE_VM
&
ously will
result in internal interference.
Because libpq makes use of malloc to store results, you will come to find
that the CLONE_VM option was not the option you were looking for.
On Tue, 2 May 2023, 19:58 Peter J. Holzer, wrote:
> On 2023-05-02 17:43:06 +0200, Michael J. Baars wrote:
>
Hi David,
My mistake. Too much fiddling around, but better than no fiddling around.
It appears both sides make mistakes, or does your freely passing around
work better than mine?
On Tue, 2 May 2023, 17:57 David G. Johnston,
wrote:
> On Tue, May 2, 2023 at 2:38 AM Michael J. Ba
I was able to
reproduce from here.
On Tue, 2 May 2023, 15:49 Laurenz Albe, wrote:
> On Tue, 2023-05-02 at 11:38 +0200, Michael J. Baars wrote:
> > I have a question about libpq and multi-threading.
> >
> > In the PostgreSQL documentation (
> https://www.postgresql.org
Hi All,
I have a question about libpq and multi-threading.
In the PostgreSQL documentation (
https://www.postgresql.org/docs/15/libpq-threading.html) it says that
results can be passed around freely between threads. However, when I try to
read the result from the parent thread, the program crashe
quot;MyTableName".
Is there settings in pssql server or db level to change it back to its
default to allow double quotes around schema.
We're using PostgreSQL 13.7 on x86_64-pc-linux-gnu, compiled by gcc (GCC)
8.5.0 20210514 (Red Hat 8.5.0-10), 64-bit
Thanks!
Michael
its WAL redo makes sure that
WAL replays until it finds the WAL record marking the end of the
backup. Grepping for XLOG_BACKUP_END (WAL record type in this case)
shows all the areas that rely on that, and xlogrecovery.c covers the
most relevant bits.
--
Michael
signature.asc
Description: PGP signature
lies on 8k on-disk pages
(default size), so it is subject to the same rules as normal relations
regarding checksums for the pages flushed to disk, even if it is on a
catalog.
--
Michael
signature.asc
Description: PGP signature
if we would be able
to put our hands on a reproducible test case that would break the
cluster so much that we'd get into this state. I don't recall seeing
this error pattern in recent history, though.
--
Michael
signature.asc
Description: PGP signature
>From the man page….
“
-s
--schema-only
Dump only the object definitions (schema), not data.
…..”
On Thu, Apr 6, 2023 at 18:40 Atul Kumar wrote:
> Hi,
>
> Please help me in telling that how I can take the backup of one single
> schema without its data using pg_dump utility ?
>
>
> So far, I
nning the perl tests, so it is isolated as much as it
can be. Using the same port should be actually fine as far as I
recall, as long as the unix socket paths are different.
--
Michael
signature.asc
Description: PGP signature
but there may
be no need to reinvent the wheel. And seeing your first message with
the requirements you list, this does what you are looking for:
- Create an empty cluster.
- Freely create databases, tablespaces, queries, etc.
- Wipe out the whole.
The test cases around src/test/recovery/t/ could be a
>From what we can ascertain, this appears to be default behavior. The thing is,
>many notes on setting this up on the interweb have examples creating the
>database user with the full name including domain.
Is it possible to do that? We are not certain where the domain name is being
stripped off.
Thanks,
Michael
Hi,
Am looking for guidance on how to fix a memory leak when using libpq
PQExecParams(). Memory leaks through CRYPTO_zalloc() and arises when using
json_agg(). None-JSON based PQExecParams() calls are not leaking.
Using Postgresql 13.6 (Ubuntu 13.6-0ubuntu0.21.10.1) on
x86_64-pc-linux-gnu, comp
com> wrote:
> On Sat, Dec 17, 2022 at 4:55 PM Michael Arnold wrote:
>
>> How do I interpret the 4 bytes of postgresql 'date' value?
>>
> See date2j and j2date in datetime.c
>
> timestamp.h has the relevant constant Tom refers to (POSTGRES_EPOCH_JDATE)
>
>
> David J.
>
>
Want to retrieve a date type from a postgres table using libpq
PQexecParams() in binary mode (please humor me).
https://www.postgresql.org/docs/14/datatype-datetime.html says that a date
is 4 bytes (4713 BC to 5874897 AD). src/include/utils/date.h defines:
typedef int32 DateADT;
Something like
On Thu, Dec 1, 2022 at 7:40 AM Vijaykumar Jain
wrote:
>
>
>> I do not recall zfs snapshots took anything resource intensive, and it was
>> quick.ill ask around for actual time.
>
>
> Ok just a small note, out ingestion pattern is write anywhere, read globally.
> So we did stop ingestion while s
t kind of environment you are using it will be hard to reach a
clear conclusion without at least more details.
--
Michael
signature.asc
Description: PGP signature
On Thu, Dec 1, 2022 at 9:21 AM Michael Loftis wrote:
>
>
>
> On Thu, Dec 1, 2022 at 06:40 Mladen Gogala wrote:
>>
>> On 11/30/22 20:41, Michael Loftis wrote:
>>
>>
>> ZFS snapshots don’t typically have much if any performance impact versus
>>
On Thu, Dec 1, 2022 at 06:40 Mladen Gogala wrote:
> On 11/30/22 20:41, Michael Loftis wrote:
>
>
> ZFS snapshots don’t typically have much if any performance impact versus
> not having a snapshot (and already being on ZFS) because it’s already doing
> COW style semantics.
>
On Wed, Nov 30, 2022 at 18:03 Mladen Gogala wrote:
> On 11/30/22 18:19, Hannes Erven wrote:
>
> You could also use a filesystem that can do atomic snapshots - like ZFS.
>
> Uh, oh. Not so sure about that. Here is a page from the world of the big
> O: https://blog.docbert.org/oracle-on-zfs/
>
> Ho
On Wed, Nov 30, 2022 at 8:40 AM Atul Kumar wrote:
>
> Hi,
>
> I have a 10TB database running on postgres 11 version running on centos 7 "on
> premises", I need to schedule the backup of this database in a faster way.
>
> The scheduled backup will be used for PITR purposes.
>
> So please let me kn
hba.conf as each HBA entry could get quite
long depending on the connection policy you may want. My take would
be to use one entry per line in an @ file in this case.
--
Michael
signature.asc
Description: PGP signature
tructs are
allowed. Unless the file name following @ is an absolute path, it is
taken to be relative to the directory containing the referencing
file."
--
Michael
signature.asc
Description: PGP signature
est release
available is 11.17, meaning that you are missing more than three years
worth of bug fixes. Based on the roadmap in [1], 11.18 should be out
next week.
[1]: https://www.postgresql.org/developer/roadmap/
--
Michael
signature.asc
Description: PGP signature
On Fri, Oct 21, 2022 at 1:52 PM Julie Nishimura
wrote:
> Hello,
> A table is constantly updated by inserting new rows. Will it affect select
> if where clause is based on > date?
> Does "where clause" to specify > date and < now?
>
You haven't described the table. Is there some kind of a date o
sight about
all that, mainly from EDB:
https://www.youtube.com/watch?v=ZbdWOuTTWrw
https://www.youtube.com/watch?v=7jVz4TTB5-4
The community wiki has a page with few references to the code of the
project:
https://wiki.postgresql.org/wiki/Zheap
--
Michael
signature.asc
Description: PGP signature
out
> of NVMe PCIe SSDs.
>
> A101 (primary) -> A201 (replica) -> B101(primary) -> B201 (replica).
replica -> primary does not really make sense for physical
replication. Or do you mean that B101 is itself a standby doing
streaming from A201?
--
Michael
signature.asc
Description: PGP signature
1 - 100 of 881 matches
Mail list logo
