Greetings,
* Bjørn T Johansen (b...@havleik.no) wrote:
> Is it possible to use one authentication method as default, like LDAP, and if
> the user is not found, then try to authenticate using
> md5/scram-sha-256 ?
Not directly in pg_hba.conf. You might be able to construct a system
which works l
Greetings,
* Benedict Holland (benedict.m.holl...@gmail.com) wrote:
> Not to get off topic, can you authenticate database users via Kerberos?
Absolutely. GSSAPI is the auth method to use for Kerberos.
Thanks!
Stephen
Greetings,
* chiru r (chir...@gmail.com) wrote:
> I am testing Pgbackrest and I have few questions.
Great!
> 1. I used postures user to perform backups and restores with Pgbackrest
> tool.
> The Trust authentication in pg_hba.conf file is working without issues.
Please don't use 'trust'.
> If
Greetings,
* Enrico Thierbach (e...@open-lab.org) wrote:
> I am using `SELECT * FROM queue ... FOR UPDATE SKIP LOCKED` to implement a
> queueing system.
>
> Now I wonder if it is possible, given the id of one of the locked rows in
> the queue table, to find out which connection/which transaction
Greetnigs,
* Enrico Thierbach (e...@open-lab.org) wrote:
> I guess with your query I can figure out which connection holds a lock, but
> it seems I cannot correlate those locks to the rows which actually are
> locked, since `pg_locks` seems not to reference this in any way.
What I gave you would
Greetings Melvin,
* Melvin Davidson (melvin6...@gmail.com) wrote:
> >I guess with your query I can figure out which connection holds a lock,
> but it seems I cannot correlate those locks to the rows which actually are
> locked, since pg_locks seems not to reference this in any way.
>
> *FWIW, I r
Greetings,
* chiru r (chir...@gmail.com) wrote:
> Please respond to my PgBackrest questions,if any one tested.
Please don't spam the lists repeatedly like this. The responses to this
mailing list are provided by the community on a volunteer basis and
repeated emails are more likely to discourage
Greetings,
* chiru r (chir...@gmail.com) wrote:
> On Wed, Mar 14, 2018 at 6:17 PM, Stephen Frost wrote:
> > * chiru r (chir...@gmail.com) wrote:
> > > I am testing Pgbackrest and I have few questions.
> >
> > Great!
> >
> > > 1. I used postu
Greetings Melvin,
* Melvin Davidson (melvin6...@gmail.com) wrote:
> On Thu, Mar 15, 2018 at 10:14 PM, Stephen Frost wrote:
> > Changes will continue to be made between major versions of PostgreSQL
> > when they're deemed necessary; I'd suggest those applications be
&g
Greetings,
Please don't top-post.
* Melvin Davidson (melvin6...@gmail.com) wrote:
> this whole discussion started because Enrico did not originally specify the
> PostgreSQL version he was working with. So after he did advise it was for
> 9.6, I felt it necessary to explain to him why a certain se
Enrico,
* Enrico Thierbach (e...@open-lab.org) wrote:
> >*FWIW, I really don't understand your need to identify the actual rows
> >that
> >are locked. Once you have identified the query that is causing a block
> >(which is usually due to "Idle in Transaction"), AFAIK the only way to
> >remedy the
Greetings,
* wambac...@posteo.de (wambac...@posteo.de) wrote:
> how can i change my mail adress for the postgresql mailing lists? adding my
> new address worked, but how do i get rid of the old one?
You'll need to change it on postgresql.org:
https://www.postgresql.org/account/
Once you've done
Greetings,
* Ron Johnson (ron.l.john...@cox.net) wrote:
> On 03/17/2018 10:51 AM, Stephen Frost wrote:
> >Once you've done that, log out of all PG sites (possibly by deleteing
> >cookies which you may have from them) and then log into postgresql.org
> >first and then
Greetings Ron,
* Ron Johnson (ron.l.john...@cox.net) wrote:
> On 03/17/2018 01:08 PM, Stephen Frost wrote:
> >* Ron Johnson (ron.l.john...@cox.net) wrote:
> >>On 03/17/2018 10:51 AM, Stephen Frost wrote:
> >>>Once you've done that, log out of all PG sites (possi
Greetings,
* Alvaro Aguayo Garcia-Rada (aagu...@opensysperu.com) wrote:
> 1. Portability. Being tied to a single database engine is not always a good
> idea. When you write business logic in database, you have to write and
> maintain your store procedures for every database engine you want to su
Greetings,
* Ravi Krishna (sravikrish...@gmail.com) wrote:
> >> I am however very comfortable with using psql and PL/pgSQL and I am very
> >opinionated.
> >
> Nothing wrong with this approach and it may very well work 90% of the time.
> Until ... a day comes when
> you need to migrate out of PG to
Greetings,
* Thomas Poty (thomas.p...@gmail.com) wrote:
> My question is : In case of a deadlock between 2 transaction, how to know
> which transaction will be canceled? Is it predictable?
The short answer is "it's whichever one detected the deadlock." The
deadlock timeout fires after a lock ha
Greetings,
* Ron (ronljohnso...@gmail.com) wrote:
> On 04/20/2018 03:55 PM, Vick Khera wrote:
> >On Fri, Apr 20, 2018 at 11:24 AM, Vikas Sharma >For anyone to offer a proper solution, you need to say what purpose your
> >encryption will serve. Does the data need to be encrypted at rest? Does it
>
Greetings,
* Ron (ronljohnso...@gmail.com) wrote:
> On 04/20/2018 06:11 PM, Stephen Frost wrote:
> >* Ron (ronljohnso...@gmail.com) wrote:
> >>On 04/20/2018 03:55 PM, Vick Khera wrote:
> >>>On Fri, Apr 20, 2018 at 11:24 AM, Vikas Sharma >>>For anyone to o
Greetings,
* John McKown (john.archie.mck...@gmail.com) wrote:
> Again, this is just a discussion point. And I'm quite willing to admit
> defeat if most people don't think that it is worth the effort.
For my 2c, at least, I do think it'd be kind of neat to have, but we'd
need a fool-proof way to
Greetings,
* Yashwanth Govinda Setty (ygovindase...@commvault.com) wrote:
> 1. Creating a big table. Identify the physical file on the disk.
> 1. While backup process is backing up a file associated with the table -
> update the rows , add a column.
> 2. Restore the server with transactio
Greetings,
* Christoph Moench-Tegeder (c...@burggraben.net) wrote:
> ## Yashwanth Govinda Setty (ygovindase...@commvault.com):
>
> > 2. Restore the server with transaction logs
>
> This is missing a lot of details. If you do it right - see your email
> thread from one week ago - you will be a
Greetings,
* Erlend Sogge Heggen (e.so...@gmail.com) wrote:
> Since it's read-only it would only be used for things like:
>
>- Fast search with advanced filters (Discourse puts PostgreSQL full text
>search to good use!)
While it might not be the case for other projects, we actually do us
Greetings,
* C GG (cgg0...@gmail.com) wrote:
> This is PostgreSQL 9.5 -- We just enabled LDAP(S) authentication (to an
> Active Directory server) for a certain grouping of users
You really shouldn't be using LDAP auth to an Active Directory system.
Active Directory supports Kerberos, which is a m
Greetings,
* C GG (cgg0...@gmail.com) wrote:
> On Wed, May 30, 2018 at 12:04 PM, Stephen Frost wrote:
> > What's the reason for wishing for them to "be able to type in a
> > password"? With GSSAPI/Kerberos, users get true single-sign-on, so they
> > woul
Greetings,
* Magnus Hagander (mag...@hagander.net) wrote:
> On Tue, Jun 5, 2018 at 4:45 PM, Chris Travers
> wrote:
> > If I may suggest: The committee should be international as well and
> > include people from around the world. The last thing we want is for it to
> > be dominated by people fro
Greetings,
* Benjamin Scherrey (scher...@proteus-tech.com) wrote:
> On Wed, Jun 6, 2018 at 2:12 AM, Christophe Pettus wrote:
> > Not at all. The need for a CoC is not theoretical. Real people,
> > recently, have left the community due to harassment, and there was no
> > system within the commun
Greetings,
* Adrian Klaver (adrian.kla...@aklaver.com) wrote:
> On 06/19/2018 03:18 PM, Asif Ali wrote:
> >just tell me the site , i dont have time to waste on shitty things , i
> >will program a spammer to send email to this list
>
> So why subscribe in the first place?
Thanks for the attempts
Greetings,
* Benjamin Scherrey (scher...@proteus-tech.com) wrote:
> One thing I recall very fondly about the early days of the Lamp stack was
> that the official documentation of PHP and MySQL was augmented with user
> created practical examples. It was still reference documentation organized
> by
Greetings Vick,
* Vick Khera (vi...@khera.org) wrote:
> I didn't know it existed either, mostly because I know how to ask google to
> do things, and the things I need to know are not covered here (yet). This
> does seem to me to be the ideal place to add more how to documentation to
> augment all
Greetings,
* Alvaro Herrera (alvhe...@2ndquadrant.com) wrote:
> I don't see why we need this thread to continue. This sounds like
> somebody looking for a solution when they don't yet know what the
> problem is.
>
> If people want to contribute, there are already some places where they
> can do
Greetings,
* Ron (ronljohnso...@gmail.com) wrote:
> We've got an old (v8.4.17, thus no parallel backups) 2.9TB database that
> needs to be migrated to a new data center and then restored to v9.6.9.
You should be using 9.6's pg_dump to perform the export. Might be a bit
annoying to do, but you sh
Greetings,
* Ron (ronljohnso...@gmail.com) wrote:
> An interesting idea. To clarify: it's possible to parallel backup a running
> 8.4 cluster remotely from a 9.6 system?
Yes, you can do a parallel backup, but you won't be able to get a
consistent snapshot. You'll need to pause all changes to th
Greetings,
* Phil Endecott (spam_from_pgsql_li...@chezphil.org) wrote:
> Dear Experts,
Since you're asking ...
> I recently set up replication for the first time. It seemed to be
> working OK in my initial tests, but didn't cope when the slave was
> down for a longer period. This is all with
Greetings,
* Phil Endecott (spam_from_pgsql_li...@chezphil.org) wrote:
> Stephen Frost wrote:
> >* Phil Endecott (spam_from_pgsql_li...@chezphil.org) wrote:
> >>archive_command = 'ssh backup test ! -f backup/postgresql/archivedir/%f &&
> >>
Greetings,
* Phil Endecott (spam_from_pgsql_li...@chezphil.org) wrote:
> OK. I think this is perhaps a documentation bug, maybe a missing
> warning when the master reads its configuration, and maybe (as you say)
> a bad default value.
If we consider it to be an issue worthy of a change then we
Greetings,
* Adrian Klaver (adrian.kla...@aklaver.com) wrote:
> On 08/12/2018 03:54 PM, Stephen Frost wrote:
> >* Phil Endecott (spam_from_pgsql_li...@chezphil.org) wrote:
> >>OK. I think this is perhaps a documentation bug, maybe a missing
> >>warning when the mas
Greetings,
* Phil Endecott (spam_from_pgsql_li...@chezphil.org) wrote:
> Adrian Klaver wrote:
> >On 08/12/2018 03:54 PM, Stephen Frost wrote:
> >>Greetings,
> >>
> >>* Phil Endecott (spam_from_pgsql_li...@chezphil.org) wrote:
> >>>OK. I think this
Greetings,
* Phil Endecott (spam_from_pgsql_li...@chezphil.org) wrote:
> Adrian Klaver wrote:
> >On 08/12/2018 02:56 PM, Phil Endecott wrote:
> >>Anyway. Do others agree that my issue was the result of
> >>wal_keep_segments=0 ?
> >
> >Only as a sub-issue of the slave losing contact with the maste
Greetings,
* Adrian Klaver (adrian.kla...@aklaver.com) wrote:
> On 08/13/2018 05:39 AM, Stephen Frost wrote:
> >* Phil Endecott (spam_from_pgsql_li...@chezphil.org) wrote:
> >>Adrian Klaver wrote:
> >>>On 08/12/2018 02:56 PM, Phil Endecott wrote:
> >>>&
Greetings,
* Adrian Klaver (adrian.kla...@aklaver.com) wrote:
> On 08/13/2018 05:08 AM, Phil Endecott wrote:
> >Adrian Klaver wrote:
> >Really? I thought the intention was that the system should be
> >able to recover reliably when the slave reconnects after a
> >period of downtime, subject only t
Greetings,
* Jack Cushman (jcush...@gmail.com) wrote:
> I have a large database of text, with a 600GB table and a 100GB table
> connected by a join table. They both see occasional updates throughout the
> week. Once a week I want to "cut a release," meaning I will clone just the
> 100GB table and
Greetings,
* Ron (ronljohnso...@gmail.com) wrote:
> On 08/14/2018 11:14 AM, Tom Lane wrote:
> >Mike Cardwell writes:
> >>pg_basebackup: could not get write-ahead log end position from server:
> >>ERROR: could not open file "./postgresql.conf~": Permission denied
> >>Now, I know what this error m
Greetings,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Unless there are substantial objections, or nontrivial changes as a result
> of this round of comments, we anticipate making the CoC official as of
> July 1 2018.
We seem to be a bit past that timeline... Do we have any update on when
this will
Greetings,
* Phil Endecott (spam_from_pgsql_li...@chezphil.org) wrote:
> David Steele wrote:
> >pgBackRest has done this for years and it saves a *lot* of headaches.
>
> The system to which I am sending the WAL files is a rsync.net
> account. I use it because of its reliability, but methods for
Greetings,
* PO (gunnar.bl...@pro-open.de) wrote:
> Consider the following scenario/setup:
> - 4 DB servers in 2 DCs
> - 1 primary (in DC1)
> - 1 sync secondary (in other DC)
> - 2 async secondaries (distributed over DCs)
I'm a bit surprised that you're ok with the latency imposed by using
Greetings,
* PO (gunnar.bl...@pro-open.de) wrote:
> Stephen Frost – Thu, 16. August 2018 19:00
> > * PO (gunnar.bl...@pro-open.de) wrote:
> > > - why does a recovery, based on a recovery.conf that points to a reachable
> > primary (which obviously communicates its own t
Greetings,
* kpi6...@gmail.com (kpi6...@gmail.com) wrote:
> The CTE mentioned below completes the query in 4.5 seconds while the regular
> query takes 66 seconds. I read from EXPLAIN ANALYSE that the regular query
> starts with a full table scan over "Doc" while the CTE joins the two tables
> firs
Greetings,
* bricklen (brick...@gmail.com) wrote:
> On Tue, Aug 14, 2018 at 10:45 AM Edmundo Robles
> wrote:
> > Is safe to upgrade from pg 9.3 to pg 10 directly using pg_upgrade or
> > is better upgrade, with pg_upgrade, from 9.3 -> 9.4 ->9.5 -> 9.6 -> 10.
>
> Using pg_upgrade, it is definit
Greetings,
* Dean Rasheed (dean.a.rash...@gmail.com) wrote:
> On 28 August 2018 at 01:49, Alvaro Herrera wrote:
> > On 2018-Aug-27, Ken Tanzer wrote:
> >>- In the scheme of things, is it a lot of work or not so much?
> >
> > Probably not much.
>
> Yeah, it doesn't seem like it would be parti
Greetings,
* Dave Peticolas (d...@krondo.com) wrote:
> On Sat, Sep 1, 2018 at 5:09 PM Adrian Klaver
> wrote:
>
> > On 09/01/2018 04:45 PM, Dave Peticolas wrote:
> >
> > > Well restoring from a backup of the primary does seem to have fixed the
> > > issue with the corrupt table.
> >
> > Pretty su
Greetings,
* Arup Rakshit (a...@zeit.io) wrote:
> I have an index defined "inspector_tool_idx4_1" UNIQUE, btree (company_id,
> item_code, deleted_at). Now I am using the *company_id* column in the where
> clause, and the selecting just the *item_code* field for all matching rows. I
> expected h
Greetings,
* Arup Rakshit (a...@zeit.io) wrote:
> I would like to ask one more question related to this topic. When I take a
> dump from production, and restore it to development DB, what are the commands
> I generally need to run to dev deb quack close to production?
The best way to get a prod
Greetings,
* Adrian Klaver (adrian.kla...@aklaver.com) wrote:
> On 9/14/18 1:31 AM, Chris Travers wrote:
> >On Wed, Sep 12, 2018 at 10:53 PM Tom Lane ><mailto:t...@sss.pgh.pa.us>> wrote:
> >
> > I wrote:
> > > Stephen Frost mailto:sfr...@snowman.
Greetings,
* Joshua D. Drake (j...@commandprompt.com) wrote:
> I think this is a complicated issue. On the one hand, postgresql.org has no
> business telling people how to act outside of postgresql.org. Full stop.
This is exactly what this CoC points out- yes, PG.Org absolutely can and
should con
Greetings,
(trimmed to -general, tho I don't know if it'll really help)
* James Keener (j...@jimkeener.com) wrote:
> > To many of us, we absolutely are a community. Remember, there are people
> > here who have been around for 20+ years, of which many have become close
> > friends, having started
Greetings,
* James Keener (j...@jimkeener.com) wrote:
> > > I fail to see how that makes everyone here part of a community anymore
> > than
> > > I'm part of the "community" of regulars at a bar I walk into for the
> > first
> > > time.
> >
> > Does the bartender get to kick you out if you get int
Greetings,
* Dimitri Maziuk (dmaz...@bmrb.wisc.edu) wrote:
> On 09/14/2018 12:46 PM, Peter Geoghegan wrote:
> > On Fri, Sep 14, 2018 at 10:31 AM, Dimitri Maziuk
> > wrote:
> >> So let me get this straight: you want to have a "sanctioned" way to deny
> >> people access to postgresql community sup
Greetings,
* Chris Travers (chris.trav...@gmail.com) wrote:
> I said I would stand aside my objections after the last point I mentioned
> them but I did not feel that my particular objection and concern with
> regard to one specific sentence added got much of a hearing. This being
> said, it is g
Greetings,
* Francisco Olarte (fola...@peoplecall.com) wrote:
> I will happily pardon brevity ( although I would not call a ten line
> sig plus a huge bottom quote "breve", and AFAIK it means the same in
> english as in spanish ) and/or typos, but the "I am not responsible"
> feels nearly insultin
Greetings,
* Yuri Kanivetsky (yuri.kanivet...@gmail.com) wrote:
> I'm trying to compile a basic set of instruction needed to set up
> continuous archiving and to recover from a backup. I'm running
> PostgreSQL 9.3 on Debian Stretch system.
9.3 is about to be end-of-life in just another month or s
Greetings,
* Ravi Krishna (srkrish...@aol.com) wrote:
> Is there a place to get all PG related security alerts? I saw this in IBM
> site:
https://www.postgresql.org/support/security/
Thanks!
Stephen
signature.asc
Description: PGP signature
Greetings,
* Torsten Förtsch (tfoertsch...@gmail.com) wrote:
> I have a table with a really small number of rows, usually about 1500,
> sometimes may be up to 5000. The usage pattern of that table is such that
> rows are inserted and kept for a while, mostly seconds or minutes but
> theoretically
Greetings,
* Matthew Pounsett (m...@conundrum.com) wrote:
> On Fri, 19 Jul 2019 at 11:25, Peter J. Holzer wrote:
> > On 2019-07-19 10:41:31 -0400, Matthew Pounsett wrote:
> > > Okay. So I guess the short answer is no, nobody really knows how to
> > > judge how much space is required for an upgra
Greetings,
* Derek Hans (derek.h...@gmail.com) wrote:
> Unfortunately only "alter function" supports "leakproof" - "alter operator"
> does not. Is there a function-equivalent for marking operators as
> leakproof? Is there any documentation for which operators/functions are
> leakproof?
Tom's quer
Greetings,
Please don't top-post on these lists.
* Derek Hans (derek.h...@gmail.com) wrote:
> Thanks for the detailed response, super helpful in understanding what's
> happening, in particular understanding the risk of not marking functions as
> leakproof. I'll take a look at the underlying code
Greetings,
* Ron (ronljohnso...@gmail.com) wrote:
> On 8/19/19 5:40 AM, Shiwangini Shishulkar wrote:
> >We have scheduled postgres full backup on centos 7 machine. DB size is
> >around 66 GB. We observed while backup is running, postmaster CPU %
> >reaches to 90 - 100%,which results very strange b
Greetings,
* Kyotaro Horiguchi (horikyota@gmail.com) wrote:
> At Mon, 19 Aug 2019 10:07:30 -0400, Stephen Frost wrote
> in <20190819140730.gh16...@tamriel.snowman.net>
> > * Ron (ronljohnso...@gmail.com) wrote:
> > > On 8/19/19 5:40 AM, Shiwangini Shishulkar wrot
Greetings,
* Vik Fearing (vik.fear...@2ndquadrant.com) wrote:
> On 19/08/2019 19:32, Tom Lane wrote:
> > "Johann 'Myrkraverk' Oskarsson" writes:
> >> I meant ALTER TYPE. Adding the send and recv functions doesn't seem
> >> to supported by ALTER TYPE.
> >> Is there a workaround for this?
> > You
Greetings,
* Vikas Sharma (shavi...@gmail.com) wrote:
> We are using postgresql 9.5 with repmgr 3.3.2 in streaming replication
> setup with 1 master and 2 slaves. I have noticed that the pg_xlog on slaves
> has grown to 200GB and is still growing.
>
> Please advise why pg_xlog is growing and not
Greetings,
* Niels Jespersen (n...@dst.dk) wrote:
>Hello Magnus
>Thank you for your prompt reply.
>I’m not sure I understand your last statement. I want to achieve that
>regardless of the case of the entered username is logged into the same
>Postgres user (whose name is create
Greetings,
* Ron (ronljohnso...@gmail.com) wrote:
> On 9/17/19 6:48 AM, David Steele wrote:
> >On 9/17/19 7:23 AM, Luca Ferrari wrote:
> >>On Tue, Sep 17, 2019 at 12:00 PM Ron wrote:
> >>>The real problem is that after doing that, "pg_ctl start -D
> >>>/path/to/new/data" fails with "PANIC: could
Greetings,
* David Steele (da...@pgmasters.net) wrote:
> On 9/17/19 10:03 PM, Stephen Frost wrote:
> > I'll get a patch into the next commitfest to remove it. The exclusive
> > method has been deprecated for quite a few releases and we should stop
> > giving bad adv
Greetings,
* Ron (ronljohnso...@gmail.com) wrote:
> On 9/18/19 8:58 PM, David Steele wrote:
> >On 9/18/19 9:40 PM, Ron wrote:
> >>I'm concerned with one pgbackrest process stepping over another one and
> >>the restore (or the "pg_ctl start" recovery phase) accidentally
> >>corrupting the productio
Greetings,
* Ron (ronljohnso...@gmail.com) wrote:
> I've been a DBA for 20+ years, and restored a **lot** of **copies** of
> production databases. PostgreSQL has some seriously different concepts.
> With every other system, it's: restore full backup to new location, restore
> differential backup,
Greetings,
* Vikas Sharma (shavi...@gmail.com) wrote:
> I am wondering which one is the best way to archive the xlogs for Backup
> and Recovery - pg_receivexlog or archive_command.
>
> pg_receivexlog seems best suited because the copied/archived file is
> streamed as it is being written to in xlo
Greetings,
* Peter Eisentraut (peter.eisentr...@2ndquadrant.com) wrote:
> On 2019-09-23 10:25, Vikas Sharma wrote:
> > I am wondering which one is the best way to archive the xlogs for Backup
> > and Recovery - pg_receivexlog or archive_command.
>
> I recommend using pg_receivexlog. It has two i
Greetings,
* Laurenz Albe (laurenz.a...@cybertec.at) wrote:
> A couple of pointers:
I generally agree with these comments.
> - This is a good setup if you don't have too many users. Metadata
> queries will start getting slow if you get into the tens of thousands
> of users, maybe earlier.
Greetings,
(we don't top-post on these lists, fyi, please reply in-line and trim)
* Matt Andrews (mattandr...@massey.com.au) wrote:
> I have little experience in this area, but it seems like having a Postgres
> role for every application user is the right way to do things. It’s just
> that it als
Greetings,
* Michael Lewis (mle...@entrata.com) wrote:
> Much of indexing strategy depends on knowing the data like how many
> distinct values and what the distribution is like. Is JsonBField->>'status'
> always set? Are those three values mentioned in this query common or rare?
> Can you re-write
Greetings,
* Aleš Zelený (zeleny.a...@gmail.com) wrote:
> But recovery on replica failed to proceed WAL file
> 00010FED0039 with log message: " invalid contrecord length
> 1956 at FED/38FFE208".
Err- you've drawn the wrong conclusion from that message (and you're
certainly not alone-
Greetings,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Stephen Frost writes:
> > * Aleš Zelený (zeleny.a...@gmail.com) wrote:
> >> But recovery on replica failed to proceed WAL file
> >> 00010FED0039 with log message: " invalid contrecord length
> &
Greetings,
* Allan Jensen (pgl...@winge-jensen.dk) wrote:
> I have GSSAPI-login and user mapping to postgres working fine.
Great!
> Whenever i login to postgres I get a line like the following in the
> logfile:
>
> connection authorized: user=testrole database=testdb SSL enabled
> (protocol=TLS
Greetings,
First off- please try to craft a new email in the future rather than
respond to an existing one. You may not realize this but there's some
headers that get copied when you do a reply that cause the email to show
up as being a reply, even if you remove all the "obvious" bits from it.
*
Greetings,
* Pól Ua Laoínecháin (lineh...@tcd.ie) wrote:
> > > 1) Is my lecturer full of it or does he really have a point?
>
> > He's full of it, as far as I can tell anyway, based on what you've
> > shared with us. Just look at the committers and the commit history to
> > PostgreSQL, and look
Greetings,
* Timmy Siu (timmy@aol.com) wrote:
> Now, my question is -
> What is the Minimum Privilege of a pgsql Backup or Replication user?
To perform a file-level backup of PostgreSQL, your OS user will need
read access to all of the files in the data directory (you can use group
privileges
Greetings,
* Ajay Pratap (ajaypra...@ameyo.com) wrote:
> I have a Centos 7 server which runs Postgresql 10.7. I am using pgbackrest
> to take db backup.
> Problem is backup is too slow.
Have you tried running 'top' to see what's going on?
> My data dir size is 9.6G and full backup runtime is 22
Greetings,
* Ariadne Conill (aria...@dereferenced.org) wrote:
> On Fri, Oct 18, 2019 at 6:01 PM Adrian Klaver
> wrote:
> > https://www.postgresql.org/docs/11/functions-json.html
> > " The field/element/path extraction operators return NULL, rather than
> > failing, if the JSON input does not hav
Greetings,
* Ariadne Conill (aria...@dereferenced.org) wrote:
> On Fri, Oct 18, 2019 at 5:57 PM Christoph Moench-Tegeder
> wrote:
> > ## Ariadne Conill (aria...@dereferenced.org):
> > > Why don't we fix the database engine to not eat data when the
> > > jsonb_set() operation fails?
> >
> > It did
Greetings,
* Dmitry Dolgov (9erthali...@gmail.com) wrote:
> If we want to change it, the question is where to stop? Essentially we have:
>
> update table set data = some_func(data, some_args_with_null);
>
> where some_func happened to be jsonb_set, but could be any strict function.
I don't
Greetings,
* Diego (mrstephenam...@gmail.com) wrote:
> I have a problem with ldap authentication, I have a ldap string like this:
>
> host all all 0.0.0.0/0 ldap ldapserver="10.20.90.251
> 10.20.90.252 10.10.90.251 10.10.90.252" ldapport=389...
>
> It is correct? if the f
Greetings,
* Christopher Pereira (krip...@imatronix.cl) wrote:
> Our stream replication slave server got out of sync so we need to base
> backup again.
If you do WAL archiving instead of depending on the WAL to exist on the
primary then a replica can catch up using WAL. Having a WAL archive
also
Greetings,
* Laurenz Albe (laurenz.a...@cybertec.at) wrote:
> On Wed, 2019-12-04 at 13:48 +0900, Michael Paquier wrote:
> > On Tue, Dec 03, 2019 at 10:32:22PM +, Julie Nishimura wrote:
> > > Hello, what is the best way to migrate from PostgreSQL 8.3.11 on
> > > x86_64-redhat-linux-gnu to Postg
Greetings,
* Zwettler Markus (OIZ) (markus.zwett...@zuerich.ch) wrote:
> with Oracle we use "backup archivelog all delete all input".
> this is a kind of atomic transaction.
> everything backuped for sure is deleted.
>
> with Postgres we archive to a local host directory
... how? Do you actuall
Greetings,
* Zwettler Markus (OIZ) (markus.zwett...@zuerich.ch) wrote:
> When there is a Postgres archiver stuck because of filled pg_xlog and archive
> directories...
>
> ... and the pg_xlog directory had been filled with dozens of GBs of xlogs...
>
> ...it takes ages until the archive_command
Greetings,
* Zwettler Markus (OIZ) (markus.zwett...@zuerich.ch) wrote:
> We use "rsync" on XFS with "wsync" mount mode. I think this should do the job?
No, that just makes sure that namespace operations are executed
synchronously, that doesn't provide any guarantee that the data has
actually been
Greetings,
* Zwettler Markus (OIZ) (markus.zwett...@zuerich.ch) wrote:
> > * Zwettler Markus (OIZ) (markus.zwett...@zuerich.ch) wrote:
> > > We use "rsync" on XFS with "wsync" mount mode. I think this should do the
> > > job?
> >
> > No, that just makes sure that namespace operations are execute
Greetings,
* Matthew Phillips (mphillip...@gmail.com) wrote:
> With the current READ UNCOMMITTED discussion happening on pgsql-hackers
> [1], It did raise a question/use-case I recently encountered and could not
> find a satisfactory solution for. If someone is attempting to poll for new
> records
Greetings,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> shigeo Hirose writes:
> > How can I pushdown of functions used in targetlist with FDW ?
>
> There is, AFAIK, no provision for that. There's not a lot of
> reason to consider adding it either, because there's no reason
> to suppose that the rem
Greetings,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Stephen Frost writes:
> > * Tom Lane (t...@sss.pgh.pa.us) wrote:
> >> There is, AFAIK, no provision for that. There's not a lot of
> >> reason to consider adding it either, because there's no reason
> &g
1 - 100 of 399 matches
Mail list logo
