Re: archive_commnad parameter question

2021-04-19 Thread Alan Hodgson
On Mon, 2021-04-19 at 21:09 +, Allie Crawford wrote: > Hello, > I am new in PostgreSQL and I am trying to understand what the “test” word is > representing in the archive_command configuration that the PostgreSQL > documentation is showing as the format on how to set up this parameter >   >

Re: archive_commnad parameter question

2021-04-19 Thread Peter J. Holzer
On 2021-04-19 21:09:13 +, Allie Crawford wrote: > I am new in PostgreSQL and I am trying to understand what the “test” word is > representing in the archive_command configuration that the PostgreSQL > documentation is showing as the format on how to set up this parameter > > archive_command =

Re: archive_commnad parameter question

2021-04-19 Thread Gavan Schneider
On 20 Apr 2021, at 7:09, Allie Crawford wrote: archive_command = 'test ! -f /mnt/server/archivedir/%f && cp %p /mnt/server/archivedir/%f' # Unix Does anybody know what is “test” representing in this parameter configuration? my_unix_prompt> man test gives: Tests the expression given

Re: archive_commnad parameter question

2021-04-19 Thread Adrian Klaver
On 4/19/21 2:09 PM, Allie Crawford wrote: Hello, I am new in PostgreSQL and I am trying to understand what the “test” word is representing in the archive_command configuration that the PostgreSQL documentation is showing as the format on how to set up this parameter archive_command = 'test

archive_commnad parameter question

2021-04-19 Thread Allie Crawford
Hello, I am new in PostgreSQL and I am trying to understand what the “test” word is representing in the archive_command configuration that the PostgreSQL documentation is showing as the format on how to set up this parameter archive_command = 'test ! -f /mnt/server/archivedir/%f && cp %p

RE: could not read from hash-join temporary file: SUCCESS && DB goes into recovery mode

2021-04-19 Thread Reid Thompson
Responses inline below Thanks, reid -Original Message- From: Tom Lane Sent: Monday, April 19, 2021 9:54 AM To: Reid Thompson Cc: pgsql-general@lists.postgresql.org Subject: Re: could not read from hash-join temporary file: SUCCESS && DB goes into recovery mode Reid Thompson writes:

RE: could not read from hash-join temporary file: SUCCESS && DB goes into recovery mode

2021-04-19 Thread Reid Thompson
Alvaro, Thanks for the responses and the explanation. It is appreciated. We will investigate re-writing the query to minimize the result set. Thanks again. reid -Original Message- From: Alvaro Herrera Sent: Monday, April 19, 2021 11:59 AM To: Reid Thompson Cc:

Re: could not read from hash-join temporary file: SUCCESS && DB goes into recovery mode

2021-04-19 Thread Alvaro Herrera
On 2021-Apr-19, Reid Thompson wrote: > Thanks - I found that, which seems to fix the error handling right? Or > does it actually correct the cause of the segfault also? Uh, what segfault? You didn't mention one. Yes, it fixes the error handling, so when the system runs out of disk space,

RE: could not read from hash-join temporary file: SUCCESS && DB goes into recovery mode

2021-04-19 Thread Reid Thompson
Thanks - I found that, which seems to fix the error handling right? Or does it actually correct the cause of the segfault also? Any suggestion on how to avoid the error until we can schedule an upgrade? Would increasing temp_buffers or some other setting for this query potentially avoid the

Re: Storing state machine

2021-04-19 Thread Mohan Radhakrishnan
After further research this may be accomplished using a 'SAGA'. The other question I was researching is the ordering of these records by timestamptz. If I have to use a orchestrator then I will pick sets of 1 records, for example, ordered by timestamptz. Should I be looking at a certain type

Re: could not read from hash-join temporary file: SUCCESS && DB goes into recovery mode

2021-04-19 Thread Alvaro Herrera
On 2021-Apr-19, Reid Thompson wrote: > Hi I'm looking for some guidance related to the subject line issue. > PostgreSQL 11.8 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 > (Red Hat 4.8.5-39), 64-bit > 128GB RAM > pgsql_tmp is on a FS with 2+TB free This bug report looks

Re: postgres in container, redirect csvlog to stderr

2021-04-19 Thread Tom Lane
=?UTF-8?Q?Filip_Rembia=C5=82kowski?= writes: > Is it possible to emit csvlog to standard output/error? No. We assume that random third-party code might write plain text messags to stderr, so trying to impose a format on that wouldn't be very successful. regards, tom

Re: could not read from hash-join temporary file: SUCCESS && DB goes into recovery mode

2021-04-19 Thread Tom Lane
Reid Thompson writes: > Hi I'm looking for some guidance related to the subject line issue. Is this repeatable? If so you've found a bug, I think. > 1. That the error message has been updated ( i.e. SUCCESS is not the > proper value) Yeah, what this really indicates is an incomplete read

Re: Question about contrib

2021-04-19 Thread Tom Lane
Guillaume Lelarge writes: > Le lun. 19 avr. 2021 à 10:43, Condor a écrit : >> Aha my mistake, sorry. Why is not in main tree then ? > Because they aren't interesting for everyone. Moreover, some are more dev > tools, than DBA tools. So better to pick the tools you need. Actually I think the

postgres in container, redirect csvlog to stderr

2021-04-19 Thread Filip Rembiałkowski
Hi. I'm running postgres in kubernetes. Is it possible to emit csvlog to standard output/error? I tried a naive & hacky work-around, by setting log_directory='/dev/fd' and log_filename='2' - but it does not work. Thanks!

Re: Storing state machine

2021-04-19 Thread Mohan Radhakrishnan
>Your requirement statement is extremely simple and I suspect you have > glossed over some of the constraints/requirements, but based on what you > have written, your requirement seems to be trivial and easily satisfied > with basic database facilities. Yes. I wasn't specific. There are

could not read from hash-join temporary file: SUCCESS && DB goes into recovery mode

2021-04-19 Thread Reid Thompson
Hi I'm looking for some guidance related to the subject line issue. PostgreSQL 11.8 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39), 64-bit 128GB RAM pgsql_tmp is on a FS with 2+TB free Information that I've been able to find on the web indicates 1. That the

Re: Question about contrib

2021-04-19 Thread Condor
On 19-04-2021 11:50, Guillaume Lelarge wrote: Le lun. 19 avr. 2021 à 10:43, Condor a écrit : On 19-04-2021 11:39, Guillaume Lelarge wrote: Hi, Le lun. 19 avr. 2021 à 09:43, Condor a écrit : Hello, I have a question about contrib directory. I know the projects there is not official

Re: Question about contrib

2021-04-19 Thread Guillaume Lelarge
Le lun. 19 avr. 2021 à 10:43, Condor a écrit : > On 19-04-2021 11:39, Guillaume Lelarge wrote: > > Hi, > > > > Le lun. 19 avr. 2021 à 09:43, Condor a écrit : > > > >> Hello, > >> > >> I have a question about contrib directory. I know the projects there > >> is > >> not official supported by

Re: Question about contrib

2021-04-19 Thread Condor
On 19-04-2021 11:39, Guillaume Lelarge wrote: Hi, Le lun. 19 avr. 2021 à 09:43, Condor a écrit : Hello, I have a question about contrib directory. I know the projects there is not official supported by PostgreSQL development team Contrib modules (as in the contrib subdirectory) are

Re: Question about contrib

2021-04-19 Thread Guillaume Lelarge
Hi, Le lun. 19 avr. 2021 à 09:43, Condor a écrit : > > Hello, > > I have a question about contrib directory. I know the projects there is > not official supported by PostgreSQL development team Contrib modules (as in the contrib subdirectory) are officially supported. -- Guillaume.

Question about contrib

2021-04-19 Thread Condor
Hello, I have a question about contrib directory. I know the projects there is not official supported by PostgreSQL development team and I wanna ask, what will be happened if the leader of project pg_crypto for example (I repeat for example) leave the project for example in pgsql 13 and

Re: Storing state machine

2021-04-19 Thread Tim Cross
Mohan Radhakrishnan writes: > Hello, >We have a workflow when we receive events into the service. But we > don't have a way to choreograph or orchestrate the workflow. The > services are all independent and receive and respond to events. > > Since there is no order imposed by the