On Friday, June 26, 2020, Samuel Williams
wrote:
> > What about, as it says, sending multiple statements in a single
> sendQuery and then polling for multiple results?
>
> I tried this, and even in single row streaming mode, I found that
> there are cases where the results would not be streamed u
> What about, as it says, sending multiple statements in a single sendQuery and
> then polling for multiple results?
I tried this, and even in single row streaming mode, I found that
there are cases where the results would not be streamed until all the
queries were sent.
>From the users point of
On Friday, June 26, 2020, Samuel Williams
wrote:
> Thanks David,
>
> You are correct.
>
> I was giving an example of what I was hoping to achieve, not what I
> expected to work with the current interface.
>
What about, as it says, sending multiple statements in a single sendQuery
and then pollin
Thanks David,
You are correct.
I was giving an example of what I was hoping to achieve, not what I
expected to work with the current interface.
I found some discussion in the past relating to batch processing which
appears to support some kind of pipelining:
https://2ndquadrant.github.io/postgr
On Friday, June 26, 2020, Samuel Williams
wrote:
> Hello,
>
> Using the asynchronous interface of libpq, is it possible to pipeline
> multiple queries?
>
> i.e.
>
> PQsendQuery(query1)
> PQsendQuery(query2)
>
> followed by
>
> query1_results = PQgetResult(...)
> query2_results = PQgetResult(...)
Hello,
Using the asynchronous interface of libpq, is it possible to pipeline
multiple queries?
i.e.
PQsendQuery(query1)
PQsendQuery(query2)
followed by
query1_results = PQgetResult(...)
query2_results = PQgetResult(...)
I tried it but got "another command is already in progress" error.
So, m
On 6/26/20 12:13 PM, Gabe Kopley wrote:
That's right Adrian, no dedicated log, but rather the messages to the
Postgres log emitted I believe here:
https://github.com/postgres/postgres/blob/REL9_6_18/src/backend/commands/vacuumlazy.c#L382
. I'm just using a regex to pull out those [removed, rema
"Brad Nicholson" writes:
> Tom Lane wrote on 2020/06/26 02:47:25 PM:
>> I'm confused about your point here. postgresql_fdw has intentionally
>> *not* been marked trusted. That's partly because it doesn't seem like
>> outside-the-database access is something we want to allow by default,
>> but i
That's right Adrian, no dedicated log, but rather the messages to the
Postgres log emitted I believe here:
https://github.com/postgres/postgres/blob/REL9_6_18/src/backend/commands/vacuumlazy.c#L382
. I'm just using a regex to pull out those [removed, remain, dead not
removable] values and plot them
On 6/26/20 12:03 PM, Brad Nicholson wrote:
Tom Lane wrote on 2020/06/26 02:47:25 PM:
> From: Tom Lane
> To: "Brad Nicholson"
> Cc: pgsql-general@lists.postgresql.org
> Date: 2020/06/26 02:51 PM
> Subject: [EXTERNAL] Re: PG13 Trusted Extension usability issue
>
> "Brad Nicholson" write
Tom Lane wrote on 2020/06/26 02:47:25 PM:
> From: Tom Lane
> To: "Brad Nicholson"
> Cc: pgsql-general@lists.postgresql.org
> Date: 2020/06/26 02:51 PM
> Subject: [EXTERNAL] Re: PG13 Trusted Extension usability issue
>
> "Brad Nicholson" writes:
> > First, as a long time user of the pgextwlist
On 6/26/20 11:47 AM, Gabe Kopley wrote:
Hi all,
Please see this graph of data points extracted from autovacuum logs:
https://imgur.com/a/OCRKoDn . It's from a 9.6 instance with default
params for autovacuum with the exceptions of autovacuum_work_mem=1
and log_autovacuum_min_duration=100.
"Brad Nicholson" writes:
> First, as a long time user of the pgextwlist extension, I'm happy to see
> this functionality appearing in core. However, as a long term user of that
> extension, I can say that ability to create an extension as a non-super
> user is pretty limited in itself in a lot of
Hi all,
Please see this graph of data points extracted from autovacuum logs:
https://imgur.com/a/OCRKoDn . It's from a 9.6 instance with default params
for autovacuum with the exceptions of autovacuum_work_mem=1 and
log_autovacuum_min_duration=100.
1. How should we interpret the # tuples rema
First, as a long time user of the pgextwlist extension, I'm happy to see
this functionality appearing in core. However, as a long term user of that
extension, I can say that ability to create an extension as a non-super
user is pretty limited in itself in a lot of cases. Many extensions both
in
Pavel Stehule writes:
> pá 26. 6. 2020 v 7:29 odesílatel Thomas Kellerer napsal:
>> Is it safe to assume that "timestamp - timestamp" will never contain units
>> larger then days?
> Now, this operator internally calls only interval_justify_hours functions.
We should probably document that --- I
On 6/26/20 6:31 AM, Matthias Apitz wrote:
Hello,
After the very successful migration of our Library Management System
(which uses ESQL/C, DBI, JDBC) together with PostgreSQL 11.4, we want to do the
same with another LMS written in Powerbuild, running in an EAServer and
currently using Sybase AS
Hi,
On Fri, Jun 26, 2020, 8:31 AM Matthias Apitz wrote:
>
> Hello,
>
> After the very successful migration of our Library Management System
> (which uses ESQL/C, DBI, JDBC) together with PostgreSQL 11.4, we want to
> do the
> same with another LMS written in Powerbuild, running in an EAServer
Hello,
After the very successful migration of our Library Management System
(which uses ESQL/C, DBI, JDBC) together with PostgreSQL 11.4, we want to do the
same with another LMS written in Powerbuild, running in an EAServer and
currently using Sybase ASE as DBS.
There is an error situation alre
"Jim Hurne" wrote on 06/24/2020 03:44:26 PM:
> That brings us to transactions. I looked for any long-running idle
> transaction (transactions that have been idle for more than 15 or 5
> minutes), but found none.
It turns out I didn't see any long running transactions because I was
using a user
Hi Stephen,
> On 22. Jun, 2020, at 19:00, Stephen Frost wrote:
> ... and all tablespaces are also on that volume. Basically, anything
> that PG might ever write to needs to all be included in that atomic
> write.
it turns out that tablespaces can be stored on different volumes if you use
consi
Hi Magnus,
> On 26. Jun, 2020, at 12:29, Magnus Hagander wrote:
> I believe NetApp does atomic snapshots across multiple volumes, if you have
> them in the same consistency group. (If you don't then you're definitely in
> for a world of pain if you ever have to restore)
>
> Snapshotting multip
On Thu, Jun 25, 2020 at 5:23 PM Paul Förster
wrote:
> Hi Ken,
>
> > On 25. Jun, 2020, at 17:15, Wolff, Ken L wrote:
> > There's actually a lot of good stuff in that document about Postgres in
> general. I'd be curious to hear what everyone thinks, though, and
> specifically about what NetApp re
Ok, thanks for the clarification.
On Thu, Jun 25, 2020 at 11:35 PM Bruce Momjian wrote:
> On Thu, Jun 25, 2020 at 04:20:06PM +0530, Bhalodiya, Chirag wrote:
> > Hi Patrick,
> >
> > Thanks for the information. I was looking for out of box postgre
> solution so
> > wanted to know how to apply foll
24 matches
Mail list logo
