On Wed, Apr 03, 2019 at 01:12:56PM -0700, Andres Freund wrote:
> I don't think VS2019 and Windows 2019 are the same thing... And the
> latter has been out for longer than yesterday... I don't know if
> anybody has done rigorous testing on it however.
Yes, it seems to me that we talk here about Wi
On Thu, Apr 11, 2019 at 11:13:17AM -0600, Michael Lewis wrote:
> Wouldn't "dead but not yet removable" be high if there were long running
> transactions holding onto old row versions?
You got it right. You need to look at the number behind the tuples
dead, but not removable which is usually a pat
On Thu, Apr 11, 2019 at 10:39:12PM -0600, Michael Lewis wrote:
> You can create (concurrently) an identical index with a new name, then drop
> old version concurrently and repeat for each. It doesn't help you figure
> out the root cause and how to prevent it from happening again, but gets you
> to
On Mon, Jun 10, 2019 at 09:00:38AM +0300, Achilleas Mantzios wrote:
> On 10/6/19 7:36 π.μ., Pawan Sharma wrote:
>> What is the best way to upgrade from PostgreSQL 9.6 to PostgreSQL
>> 11 instead of pg_upgrade.
>
> why not pg_upgrade ? If the size is near the 3TB mark as you say,
> pg_upgrade is the
On Wed, Jun 26, 2019 at 02:08:19PM -0400, Brad Nicholson wrote:
> In testing, it doesn't appear to matter. I've ensured that I've generated
> some full page writes (confirmed via pg_waldump), and those apply
> fine.
Full pages writes are first written from shared buffers to WAL, where
their check
On Fri, Jun 28, 2019 at 07:43:30AM -0400, Brad Nicholson wrote:
> So if all the checksums are being recalculated on the replica, this
> approach should be relatively safe, should it not?
Yep.
> Assuming pg_checksums is doing the right thing (and it looks to me like it
> should be).
The constrain
On Sun, May 07, 2023 at 10:30:52PM +1200, Thomas Munro wrote:
> Bug-in-PostgreSQL explanations could include that we forgot it was
> dirty, or some backend wrote it out to the wrong file; but if we were
> forgetting something like permanent or dirty, would there be a more
> systematic failure? Oh,
On Mon, May 08, 2023 at 02:46:37PM +1200, Thomas Munro wrote:
> That sounds like good news, but I'm still confused: do you see all 0s
> in the target database (popo)'s catalogs, as reported (and if so can
> you explain how they got there?), or is it regression that is
> corrupted in more subtle way
On Mon, May 08, 2023 at 07:15:20PM +0530, Dilip Kumar wrote:
> I am able to reproduce this using the steps given above, I am also
> trying to analyze this further. I will send the update once I get
> some clue.
Have you been able to reproduce this on HEAD or at the top of
REL_15_STABLE, or is tha
On Mon, May 08, 2023 at 06:04:23PM -0400, Tom Lane wrote:
> Andres seems to think it's a problem with aborting a DROP DATABASE.
> Adding more data might serve to make the window wider, perhaps.
And the odds get indeed much better once I use these two toys:
CREATE OR REPLACE FUNCTION create_tables(
On Thu, Jun 22, 2023 at 07:16:21PM +0530, Abhishek Dasgupta wrote:
> I am puzzled as to why this error occurs only with PostgreSQL 14 and not
> with PostgreSQL 11.
This error is specific to the Postgres JDBC driver, which relies on
its own application layer for FIPS and SCRAM because it speaks
dir
On Fri, Jun 23, 2023 at 12:21:48AM -0400, Juan Rodrigo Alejandro Burgos Mella
wrote:
> I have a modified version of ECPG, to which I gave the ability to do
> semantic analysis of SQL statements. Where can you share it or with whom
> can I discuss it?
I cannot say what kind of problem this solves
On Tue, Jul 18, 2023 at 04:50:25PM +0800, Pandora wrote:
> I found that starting from version 9.5, PostgreSQL will do fsync on
> the entire data directory after DB crash. Here's a question: if I
> have FPW = on, why is this step still necessary?
Yes, see around the call of SyncDataDirectory() in x
On Wed, Jul 26, 2023 at 05:33:50PM +0530, Praneel Devisetty wrote:
> Standy is not picking this change even after a reload.
>
> Restarting standby is working out, but as PG13 supports reload of
> primary_connfino is there a reliable way to achieve this without restarting
> standby database.
prima
On Tue, Jul 18, 2023 at 01:53:23AM +0200, Gert Cuykens wrote:
> Hi, suggest to automatically rename backup_manifest to backup_manifest.old
> like backup_label when postgres start up successfully because it has no use
> anymore for pg_verifybackup after postgres has been started.
Yes, I would agree
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
On Tue, Oct 03, 2023 at 06:31:27AM +0200, Laurenz Albe wrote:
> On Tue, 2023-10-03 at 12:33 +1100, rob stone wrote:
>> Would running CLUSTER on the table use the new parameters for the re-
>> write?
>
> No, as far as I know.
Note that under the hoods VACUUM FULL and CLUSTER use the same code
path
On Tue, Oct 03, 2023 at 09:08:49AM +0200, Dominique Devienne wrote:
> In my case, it's OK not to be transactional, for these experiments. Is
> there a way
> to lock the table and do the rewriting w/o generating any WAL? I don't have
> any experience
> with unlogged tables, but should I take an exc
On Thu, Oct 12, 2023 at 09:42:47AM +0900, Abhishek Bhola wrote:
> For most of the Postgres errors, translating it to WARNING level in syslog
> works, however, I wanted to translate *ERROR codes XX000/1/2* in Postgres
> to be ERROR in syslog as well, so that it triggers the alert system and I
> can
On Wed, Oct 25, 2023 at 11:33:11AM +0200, Andreas Kretschmer wrote:
> Am 25.10.23 um 11:24 schrieb Matthias Apitz:
>> We have a client who run REINDEX in certain tables of the database of
>> our application (on Linux with PostgreSQL 13.x):
>>
>> REINDEX TABLE CONCURRENTLY d83last;
>> REINDEX TABLE
On Sun, Oct 29, 2023 at 11:49:11AM +0100, Peter J. Holzer wrote:
> On 2023-10-29 10:11:07 +0100, Paul Förster wrote:
>> On Oct 29, 2023, at 02:43, Peter J. Holzer wrote:
>>> I don't think so. AFAIK Replication keeps the data files in sync on a
>>> bit-for-bit level and turning on checksums changes
On Fri, Dec 22, 2023 at 10:55:24AM +0200, Kouber Saparev wrote:
> The table for this file node is not even included in any of the
> publications we have. I've found a similar issue described [1] before, so I
> was wondering whether this patch is applied? Our subscriber database is
> PostgreSQL 16.1
On Thu, Dec 28, 2023 at 02:03:12PM +0200, Kouber Saparev wrote:
>> The first problem that we 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/
>
> Thank you. Is there a bug report or should we file one? It
On Thu, Feb 01, 2024 at 07:37:32AM +, ma lz wrote:
> session 1:
> create temp table ttt ( a int );
> insert into ttt values(3); -- query_id is XXX from
> pg_stat_activity
>
> session 2:
> create temp table ttt ( a int );
> insert into ttt values(3);
On Tue, Mar 26, 2024 at 06:22:32PM -0400, Isaac Morland wrote:
> I use a script to restore a backup to create a testing copy of the
> database. I set the following in postgresql.auto.conf:
>
> recovery_target = 'immediate'
> recovery_target_action = 'promote'
Why not, after a pg_basebackup -R I a
On Wed, Jun 26, 2024 at 02:43:30PM +, Andrew Longwill wrote:
> We’re using Postgresql 15.4 in AWS RDS. Since yesterday we have seen
> two occurrences where our PHP application becomes unable to connect
> to our RDS replicas. In the application logs we see the error
> "FATAL: could not attach to
On Thu, Jun 27, 2024 at 09:19:45AM +0500, Kashif Zeeshan wrote:
> It's hard to figure out the issue by just looking on the process list, to
> figure out the issue you need to share the DB Server Logs and thats the why
> to figure out the exac issue.
Note that it is equally hard for anybody reading
On Fri, Mar 05, 2021 at 07:36:37PM +0200, Andrus wrote:
> Then turned real-time protection off:
>
> Problem persists. New entry is written after every 10 seconds.
On which files are those complaints? It seems to me that you may have
more going on in this system that interacts with your data fold
On Sat, Mar 06, 2021 at 07:53:11PM +0200, Andrus wrote:
> I changed wal_recycle to off. So checkpointer should no more try to rename
> wal files. Iit still tries to rename files. No idea way it does not use this
> setting:
On Windows, RemoveXlogFile() would still rename a given WAL segment
file wi
On Sun, Mar 07, 2021 at 11:45:26AM +0200, Andrus wrote:
> Should files with .deleted extension deleted manually to save disk space ?
> May of them have dates before today.
RemoveOldXlogFiles() would discard any of those .deleted files because
they don't match a legal WAL segment name, so checkpoin
Hi Jan,
On Fri, Mar 12, 2021 at 06:13:33PM -0500, Jan Wieck wrote:
> One of the things in my way is that when using pg_resetwal to put the
> NextXID way into the future (to push the old cluster close to wraparound for
> example), the postmaster won't start because it doesn't have the pg_xact
> fil
On Sat, Mar 13, 2021 at 12:03:04PM -0800, Adrian Klaver wrote:
> So, the 10 instance is not running and the 9.5 instance is listening on the
> default port. At this point I would leave things as they are.
Robert, you may want to know that 9.5 has been EOL'd by community.
Just saying.
--
Michael
Hi Andrus,
On Wed, Mar 10, 2021 at 03:20:47PM +0200, Andrus wrote:
> After re-starting postgres service problem persists.
Where you getting the Postgres binaries from? If we provide a patch,
could you test it? This would require that you do your own build,
unfortunately, but having an environme
same error as yours.
In one of those servers, do you have in pg_wal/ some files named
xlogtemp.N? N is an integer that would be the PID of the process that
generated it.
--
Michael
From 961f9a03d4c27220c33e88402d5ef274424a0ab2 Mon Sep 17 00:00:00 2001
From: Michael Pa
On Wed, Mar 17, 2021 at 01:09:24AM +0200, Andrus wrote:
> Should I try install Visual C++ , compile and replace postgres.exe file in
> AMD server.
Mostly. That's the annoying part:
https://www.postgresql.org/docs/devel/install-windows-full.html
It is also possible to compile the code on a first
On Wed, Mar 17, 2021 at 09:25:00AM +0200, Andrus wrote:
> pg_config --configure outputs
>
> --enable-thread-safety --enable-nls --with-ldap --with-openssl --with-uuid
> --with-libxml --with-libxslt --with-icu --with-tcl --with-perl --with-python
Thanks. Do you actually use OpenSSL, LDAP, uuid-os
On Wed, Mar 17, 2021 at 11:44:48AM -0400, Tom Lane wrote:
> Oh! That's an interesting theory; it'd explain why this broke recently,
> because we didn't use to use that function. But how do you draw that
> conclusion from this stack trace?
>
> Anyway, if you've diagnosed this correctly, I bet the
On Wed, Mar 17, 2021 at 10:45:28AM +0200, Andrus wrote:
> In this server hopefully no. Application code contains xml parsing it but
> probably those queries are never running in this server.
Okay, cool. I am going to send you privately two links to the builds
I am going to produce, 13.2 unpatched
On Thu, Mar 18, 2021 at 12:25:45PM +1300, Guy Burgess wrote:
> FWIW, this looks the same issue I am getting (reported last month:
> https://www.postgresql.org/message-id/f444a84e-2d29-55f9-51a6-a5dcea3bc253%40burgess.co.nz)
Yep.
> I get the same Process Monitor output, including BUFFER OVERFLOW e
On Fri, Mar 19, 2021 at 09:00:10AM +0200, Andrus wrote:
> I replaced files in 13.1 server with ones from your patched version. There
> are no errors in log file now for 8 hours.
Yippee. Thanks.
Have you tested the unpatched builds? And did you see some errors
with them?
--
Michael
signature.a
On Tue, Feb 16, 2021 at 12:22:36PM +0100, Thomas Kellerer wrote:
> My first suspect is always the anti-virus on Windows when things like
> that happen with Postgres.
Or maybe not. 13 has introduced a regression in this area AFAIK, and
909b449 should have taken care of it (available in 13.3~).
--
On Mon, Mar 22, 2021 at 09:25:26AM +0200, Andrus wrote:
> Errors in pg_wal directory seems not to occur in patched version. Errors in
> pg_stat_tmp still occur. Yesterdays log introduces new error message
>
> using stale statistics instead of current ones because stats collector is
> not respondin
On Mon, May 03, 2021 at 11:10:44AM -0400, Jan Wieck wrote:
> Not yet, but I will enter it so that we can get it into 15 for sure.
I may be missing something but this is not listed:
https://commitfest.postgresql.org/33/
Could you add it to the CF app please? There are so many patches and
discussi
On Wed, Jul 28, 2021 at 06:51:22AM +, M Tarkeshwar Rao wrote:
> We are working on a activity in which I need to refresh the TLS
> certificate without restarting the my application pod.
> This feature is already there in Postgres. Can anyone please suggest
> us how postgres is implemented the s
On Sun, Oct 17, 2021 at 10:33:52PM +0200, Daniel Verite wrote:
> However lz4 appears to be much faster to compress than pglz, so its
> benefit is clear in terms of CPU usage for future insertions.
CPU-speaking, LZ4 is *much* faster than pglz when it comes to
compression or decompression with its d
On Sun, Oct 17, 2021 at 10:13:48PM +0300, Florents Tselai wrote:
> I did look into VACUUM(full) for it’s PROCESS_TOAST option which
> makes sense, but the thing is I already had a cron-ed VACUUM (full)
> which I ended up disabling a while back; exactly because of the
> double-space requirement.
Pl
On Mon, Oct 18, 2021 at 09:57:11AM +0300, Florents Tselai wrote:
> Oh, that’s good to know then. So besides ALTER COMPRESSION for
> future inserts there’s not much one can do for pre-existing values
The posting style of the mailing list is to not top-post, so if you
could avoid breaking the logic
On Mon, Oct 18, 2021 at 08:01:04AM -0700, Adrian Klaver wrote:
> Not sure how much this applies to the Postgres usage of lz4. As I understand
> it, this is only used internally for table compression. When using pg_dump
> compression gzip is used. Unless you pipe plain text output through some
> oth
On Wed, Nov 10, 2021 at 08:36:45PM -0500, Rita wrote:
> Yes, I have read the manual and seen this. It pauses the replication
> (select pg_is_wal_replay_paused()). But on the primary, when I look at
> pg_stat_replication, it still says 'streaming' in the state column. My
> question was how do I get
On Mon, Nov 29, 2021 at 12:12:11PM +0100, Paul van Rixel wrote:
> Now the postgresql.logs are polluted with log connections/disconnection,
> Agent monitoring entries and in between some entries which need some
> attention but you missed them. I know the option exists to disable
> log_(dis)connectio
On Tue, Dec 14, 2021 at 05:25:04AM +0100, Marc Millas wrote:
> My question: as the synchronous option is supposed to make pg_receivewal
> write transaction immediately in the wal files, is there a way to ask the
> standby to apply them on the fly ie. without waiting a wal file change ?
Nope, there
On Wed, Dec 15, 2021 at 12:15:27AM -0300, Martín Fernández wrote:
> The reindex went fine in the primary database and in one of our
> standby. The other standby that we also operate for some reason
> ended up in a state where all transactions were locked by the WAL
> process and the WAL process was
On Mon, Dec 20, 2021 at 03:22:31PM +0100, Christoph Moench-Tegeder wrote:
> Active FIPS mode (/proc/sys/crypto/fips_enabled => 1) on the server does
> produce this behaviour.
Most likely, this is a build linked with OpenSSL? The way MD5 hashes
are computed in Postgres has largely changed in 14, a
On Tue, Jan 04, 2022 at 12:54:35PM -0500, Tom Lane wrote:
> I reproduced this on Fedora 35 with FIPS mode enabled. The problem
> is that OpenSSL treats MD5 as a disallowed cipher type under FIPS
> mode, so this call in pg_cryptohash_init fails:
Is that 3.0.0 or 1.1.1? I can see the following, te
On Wed, Jan 05, 2022 at 01:08:53AM -0500, Tom Lane wrote:
> I think it's very important that the error message in this case
> mention "FIPS mode" explicitly. Otherwise, people will have no
> idea that that's where the problem originates, and they'll be
> frustrated and we'll get bug reports. (The
On Wed, Jan 05, 2022 at 04:09:12PM +0900, Michael Paquier wrote:
> In order to make things portable with 14 in cryptohash.c, we don't
> have any need to change the existing cryptohash APIs. We could just
> store in each implementation context a location to a static string,
> and
etail in
md5_crypt_verify() and plain_crypt_verify() to feed back a LOG entry
to the postmaster on those failures, and saw that it is safe to assign
directly the error returned by the cryptohash APIs, avoiding the
extra psprintf call that could become an issue under memory pressure.
What do you thin
b309ce64d8f6fea7a714da08df56c Mon Sep 17 00:00:00 2001
From: Michael Paquier
Date: Sat, 8 Jan 2022 14:56:39 +0900
Subject: [PATCH v3] Improve error reporting for cryptohashes
---
src/include/common/cryptohash.h | 1 +
src/include/common/md5.h | 9 ++-
src/include
On Sat, Jan 08, 2022 at 02:00:16PM -0500, Tom Lane wrote:
> This is looking pretty solid to me. Just a couple of nitpicks:
>
> * In most places you initialize variables holding error strings to NULL:
>
> + const char *logdetail = NULL;
>
> but there are three or so spots that don't, eg Perf
On Mon, Jan 17, 2022 at 05:05:52PM +0100, Carla Iriberri wrote:
> I saw previous discussions where different errors were logged with the
> "Success"
> message and this was corrected/treated as a bug, but I couldn't find similar
> reports specific to "could not accept SSL connection". Is this a know
On Thu, Jan 20, 2022 at 09:05:35AM +1300, Thomas Munro wrote:
> Good news, I'm glad they nailed that down. I recall that this
> behaviour was a bit of a moving target in earlier versions:
>
> https://www.postgresql.org/message-id/CAEepm%3D3cc5wYv%3DX4Nzy7VOUkdHBiJs9bpLzqtqJWxdDUp5DiPQ%40mail.gmai
On Wed, Jan 19, 2022 at 07:58:43PM -0500, Tom Lane wrote:
> Personally I'm satisfied to leave it as-is, since this issue apparently
> occurs only in a minority of OpenSSL versions, and not the newest.
Leaving things in their current state is fine by me. Would it be
better to add a note about the
On Wed, Jan 19, 2022 at 08:06:30PM -0500, Tom Lane wrote:
> Michael Paquier writes:
> > Leaving things in their current state is fine by me. Would it be
> > better to add a note about the business with 3.0 though?
>
> What do you envision saying? "We don't nee
On Fri, Jan 21, 2022 at 01:38:59PM +0100, Matthias Apitz wrote:
> Does the PostgreSQL (11.4 or 13.1) record somewhere in system tables
> the creation of INDEXes (or other objects)?
Hard to say what you are looking for with such a general question.
Would pg_index or pg_indexes be enough? There ar
On Sat, Jan 08, 2022 at 08:12:50AM -0800, Adrian Klaver wrote:
> On 1/8/22 05:21, Ali Koca wrote:
>> I can't understand functions in md5.h, these are seemingly little bit
>> weird. Such as:
>> /* Utilities common to all the MD5 implementations,
>> as of md5_common.c */
>> extern bool
On Wed, Jan 26, 2022 at 05:30:01PM -0800, Ben Chobot wrote:
> We do a lot of queries per day, over a lot of hosts, all of which are on
> 12.9. We've recently started doing a better job at analyzing our db logs and
> have found that, a few times a day, every day, we see some of our queries
> fail wi
On Wed, Nov 22, 2017 at 10:31 AM, Craig Ringer wrote:
> On 22 November 2017 at 08:43, Jankirk.Vincent., Jamison
> wrote:
>> I am entirely very new to PG development.
>>
>> Currently, I’m studying the test suites, and I feel the more experienced
>> PG devs here could provide some insights on testi
On Fri, Nov 24, 2017 at 10:27 AM, Jankirk.Vincent., Jamison
wrote:
> I will take note of all your advice. I think it's because I've noticed that a
> lot of functions and lines are still not covered by tests
> (https://coverage.postgresql.org/), so I feel like I want to work on tests
> first whi
On Thu, Nov 23, 2017 at 1:28 AM, Alexander Pyhalov wrote:
> On 11/22/17 07:24 PM, Magnus Hagander wrote:
>> What is your postgres version, and what's the "version history" of
>> upgrades
>> from it (talking pg_upgrade upgrades, not dump/reload upgrades). This
>> might
>> be fallout from old bugs t
On Thu, Nov 30, 2017 at 3:01 PM, tao tony wrote:
> hi dears,
>
>
> I'm using copy and jdbc copyin to build load data to pg,data type in table
> is jsonb.postgresql version are 9.6 and 10.0.
>
> Some records with escape characters would be failed with error"ERROR:
> invalid input syntax for type js
On Mon, Dec 4, 2017 at 9:39 AM, Tom Lane wrote:
> Ah. The problem here is that "json_rmq->>'totalSize'" leaks some memory
> on each execution, and it's executed again for each row produced by the
> json_array_elements() SRF, and the memory can't be reclaimed until we've
> finished the full output
On Mon, Dec 4, 2017 at 9:03 PM, Martin Moore wrote:
> After a few days, it’s noticeable that the Postgres on the publisher node is
> constantly using a lot of cpu (26% today) and having a big impact on the
> system performance even when doing very little. Logging on to the subscriber
> and remo
On Tue, Dec 5, 2017 at 6:12 AM, Alvaro Herrera wrote:
> sql2pg wrote:
>> how about uncommitted(open transactions) . if a segment has 1 committed and
>> 2 uncommitted transactions then will it keep the segment instead deleting it
>> after checkpoint , since it has 2 uncommitted transactions
>
> Th
On Thu, Dec 7, 2017 at 1:18 PM, Dylan Luong wrote:
> How do we clean up the pgsql_tmp folder? Will Postgres periodically clean
> it? Ie CHECKPOINT?
A postmaster restart cleans up those files automatically.
--
Michael
On Thu, Dec 21, 2017 at 12:24:25PM +, Virendra Shaktawat - Quipment India
wrote:
> [Quipment Logo]
> I have stuck at foreign data wrapper. I am accessing the form MS Sql Server.
> Foreign table has been created with data. unfortunately I am unable to
> perform DML operation like insert, upda
On Mon, Dec 25, 2017 at 06:12:05PM -0500, Melvin Davidson wrote:
> On Mon, Dec 25, 2017 at 1:28 PM, nikhil raj wrote:
>> Hi guys ,
>> when check the task manager I see these many postgres.exe are running. How
>> to identify which pid is running for which process please any one can help
>> me out.
On Wed, Dec 27, 2017 at 12:27:05AM +0100, Alban Hertroys wrote:
>
>> On 26 Dec 2017, at 18:11, Alvaro Herrera wrote:
>
> …
>
> > 3. configure and make
> > ./configure
> > make
> > make install
>
> …
>
> > For the options in step 3 you could use whatever your current server
> > has; use
On Tue, Dec 26, 2017 at 11:04:55AM +0100, Michelle Konzack wrote:
> I like to make the partitions smaller, but the documentation say, you
> should not dare to make several 1000 partitions..
Even more than a hundred may be already risky in my opinion here. The
issue with a large number of partition
On Wed, Dec 27, 2017 at 08:53:11AM +0100, Michelle Konzack wrote:
> Is there already a release date for v11?
Based on the pace of the most recent major releases, this could happen
around September. This depends on any issues encountered
post-development though.
--
Michael
signature.asc
Descripti
On Fri, Dec 29, 2017 at 11:47:01AM +0100, hmidi slim wrote:
> I'm trying to understand the utility of pool connection, I found that it's
> useful to enhance the performance of a database. However I want to know if
> it is a good option to put a large number in max_connection option to
> handle a la
On Wed, Jan 03, 2018 at 02:53:27PM +, Goli, Vijay wrote:
> As per our Organization standards, we need to have the below limitations:
>
> 1. Password length should be minimum of 15 characters.
> 2. Password should contain at least one digit, one upper and lower
> case character and one
On Fri, Dec 15, 2017 at 12:03:08PM -0500, Tiffany Thang wrote:
> 1. set up a read-only slave database? The closest solution I could find is
> Hot Standby but the slave would not be accessible until after a
> failover.
That's what the parameter hot_standby is for in recovery.conf. When a
server is
On Fri, Jan 5, 2018 at 3:58 AM, Tiffany Thang wrote:
> Thanks for your input. What I meant to say was rolling back all the changes.
> I was hoping for a way to temporary open the read-only standby in r/w for
> testing purpose and then rollback all the changes made during the test
> without having
On Tue, Jan 09, 2018 at 12:54:18AM +0100, Rakesh Kumar wrote:
> Can somebody tell us how many partitions are good number without
> impacting the performance. We are hearing around a thousand, is that a
> limit. Do we have plan to increase the number of partitions for a
> table. We would appreciate
On Thu, Jan 11, 2018 at 04:58:02PM +, Dylan Luong wrote:
> The steps I took were:
>
> 1. Stop all watchdogs
>
> 2. Start/stop the old master
>
> 3. Run 'checkpoint' on new master
>
> 4. Run the pg_rewind on old master to resync with new master
>
> 5. Start the
On Thu, Jan 11, 2018 at 04:40:30PM +0100, Alban Hertroys wrote:
> What is a good approach here?
By having a some point an origin and target table in the same cluster,
you would just need to define things properly. I have not checked, but
perhaps this is the kind of use cases where pg_partman
(http
On Fri, Jan 12, 2018 at 09:44:25PM +, Dylan Luong wrote:
> The file exist in the archive directory of the old master but it is
> for the previous timeline, ie 5 and not 6, ie
> 0005038300BE. Can I just rename the file to 6 timeline? Ie
> 0006038300BE
What are the conte
On Mon, Jan 15, 2018 at 12:13:46AM +, Dylan Luong wrote:
> The content of the history file 0006.history is:
Please do not top-post. This breaks the logic of the thread.
> $ more 0006.history
> 1 2CE/8A98no recovery target specified
> 2 2CE/FF974EF0no recovery t
On Mon, Jan 15, 2018 at 07:13:28PM -0700, Rob Sargent wrote:
> On successful completion, an INSERT command returns a command tag of
> the form
>
> INSERT oid count
> The count is the number of rows inserted or updated. If count is
> exactly one, and the target table has OIDs, then oid is the OID
>
On Tue, Jan 16, 2018 at 07:05:19PM +0100, Adam Sjøgren wrote:
> This sounds very interesting - we are running PostgreSQL 9.3.20.
Which means that we may be looking at a new bug, 9.3.20 is the latest in
the 9.3 set as of today.
> Did you ever find out exactly what the change that solved the proble
On Wed, Jan 17, 2018 at 12:16:19PM -0500, Tom Lane wrote:
> The basic thrust of these messages is "I'm reading what should be
> sequentially numbered data chunks for this toast OID, and the sequence
> numbers are wrong". Both of these instances could be explained by
> duplicate toast rows (or dupl
On Fri, Jan 19, 2018 at 03:40:01PM +, Raymond O'Donnell wrote:
> On 19/01/18 15:34, hmidi slim wrote:
>> Hi,
>> I'm looking for a function in postgresql which notify the client if a
>> table was full or not.So I found the function Notify
>> https://www.postgresql.org/docs/9.0/static/sql-notify.
On Sun, Jan 21, 2018 at 11:57:39AM -0700, Sherman Willden wrote:
> Basic question 1: Which non-networked front-end would work best for me?
>
> Basic question 2: I am seriously considering HTML fields to capture and
> process the information. So to connect with postgresql what do I need to
> know?
On Thu, Jan 25, 2018 at 08:21:43PM -0500, Stephen Frost wrote:
> That's correct, which is why it's encouraged to have multiple replicas
> configured when using synchronous replication. In v10, it's possible to
> specify how many synchronous replicas are required to have acknowledged
> a given tran
On Wed, Jan 31, 2018 at 10:52:38AM -0600, Alexander Stoddard wrote:
> If a table is set to unlogged is it inherently non-durable? That, is any
> crash or unsafe shutdown _must_ result in truncation upon recovery?
Yes, they are designed like that. Upon recovery all unlogged tables are
re-initializ
On Tue, Feb 06, 2018 at 12:50:56AM -0600, Jeremy Finzel wrote:
> The table I am setting to logged is 32GB with indexes. I see it writing
> WAL files like crazy but after about an hour and a half, it has written out
> some 2500 WAL segments, then it just sits and continues to run as "active",
> but
On Tue, Feb 06, 2018 at 01:36:04AM -0600, Jeremy Finzel wrote:
> Here is the basic structure - is the gist index significant?:
>
> CREATE UNLOGGED TABLE foo (
> as_of_date daterange NOT NULL,
> customer_id integer,
> bunch_of_fields_here);
>
> ALTER TABLE ONLY foo
> ADD CONSTRAINT
On Tue, Feb 06, 2018 at 03:58:14PM +, Raymond O'Donnell wrote:
> On 06/02/18 13:25, Thiemo Kellner, NHC Barhufpflege wrote:
>> But why do I get following error?
>> ERROR: function gen_random_uuid() does not exist.
>> create table ENTITY (ID uuid not null default gen_random_uuid());
>
> Only a
On Wed, Feb 07, 2018 at 11:35:13AM -0600, Jeremy Finzel wrote:
> I was able to get it to finish by just waiting awhile. To give you an
> idea, the table with no indexes was set logged in 7 minutes. With the gist
> index, it took 3 hours but finally finished. It is only writing WAL for
> about th
On Mon, Feb 12, 2018 at 03:23:22PM +, GALLIANO Nicolas wrote:
> I'm trying to backup a remote DB (9.6.6) using barman 2.3 but backup
> failed start.
> In barman.log i've such errors :
It would be a better idea to contact directly the maintainers of the
project here:
http://www.pgbarman.org/su
201 - 300 of 311 matches
Mail list logo
