On 6/1/22 22:38, Robert Haas wrote:
> On Sat, May 28, 2022 at 4:51 PM Tomas Vondra
> wrote:
>> Yeah, I think that might/should work. We could still create the HOT
>> chain, but we'd have to update the BRIN indexes. But that seems like a
>> fairly complicated change to be done this late for PG15.
>
On Sat, Jun 04, 2022 at 08:42:33PM -0500, Justin Pryzby wrote:
> The fix seems to be to CHECK_FOR_INTERRUPTS() within multi_sort_compare().
> That would supercede the other two CHECK_FOR_INTERRUPTS I'd proposed, and
> handle mcv, depends, and ndistinct all at once.
Hmm. I have to admit that addin
On Mon, Jun 06, 2022 at 09:08:08AM +0200, Tomas Vondra wrote:
> Attached is a patch reverting both commits (5753d4ee32 and fe60b67250).
> This changes the IndexAmRoutine struct, so it's an ABI break. That's not
> great post-beta :-( In principle we might also leave amhotblocking in
> the struct but
On Tue, May 24, 2022 at 08:08:26PM +0200, Peter Eisentraut wrote:
> On 18.05.22 21:48, Andres Freund wrote:
>> - GETTIMEOFDAY_1ARG - test doesn't exist - I suspect it might not be
>> necessary
>
> Might be obsolete, consider removing.
I just came across this one independently of what you are doi
On Mon, Jun 6, 2022 1:14 PM vignesh C wrote:
>
> The attached v18 patch has the fixes for the same.
>
Thanks for updating the patch, here are some comments.
0002 patch
==
1.
+
+origin (string)
+
+
It maybe better if the type of "origin" parameter
Dear PostgreSQL Hacker Community,
I am facing a tricky bug which makes the Query Planner crashes when using
COUNT(*) function.
Without any upgrade suddenly a table of a database instance could not be
queried this way:
SELECT COUNT(*) FROM items;
-- ERROR: variable not found in subplan target
Dear hackers,
I found another use-case for LRG. It might be helpful for migration.
LRG for migration
--
LRG may be helpful for machine migration, OS upgrade,
or PostgreSQL itself upgrade.
Assumes that users want to migrate database to other environment,
e
On Sat, Jun 4, 2022 at 9:39 AM Bharath Rupireddy
wrote:
>
> On Sat, Jun 4, 2022 at 6:29 PM James Coleman wrote:
> >
> > A few weeks back I sent a bug report [1] directly to the -bugs mailing
> > list, and I haven't seen any activity on it (maybe this is because I
> > emailed directly instead of u
On Mon, Jun 6, 2022 at 1:26 AM Kyotaro Horiguchi
wrote:
>
> At Sat, 4 Jun 2022 19:09:41 +0530, Bharath Rupireddy
> wrote in
> > On Sat, Jun 4, 2022 at 6:29 PM James Coleman wrote:
> > >
> > > A few weeks back I sent a bug report [1] directly to the -bugs mailing
> > > list, and I haven't seen a
Hi, hackers
I just wrote a test code for the `pg_buffercache` extension which
doesn't not have test code.
I wrote the sql query to ensure that the buffer cache results are the
same when `make installcheck` is performed.
---
regards
Lee Dong Wook.
0001_add_test_pg_buffercache.patch
Description: B
On Tue, Apr 12, 2022 at 11:19:40AM -0400, Tom Lane wrote:
> "Jonathan S. Katz" writes:
> > On 4/11/22 4:11 PM, Tom Lane wrote:
> >> This idea does somewhat address my unhappiness upthread about printing
> >> values with source = 'internal', but I see that it gets confused by
> >> some GUCs with cu
On Mon, Jun 06, 2022 at 09:34:24AM +, Jean Landercy - BEEODIVERSITY wrote:
> Faulty setup is about:
>
> SELECT version();
>
> -- PostgreSQL 13.6 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu
> 7.5.0-3ubuntu1~18.04) 7.5.0, 64-bit
Please check if the problem occurs in v13.7
https://www.pos
Hi Tomas,
> Hi,
>
> At on of the pgcon unconference sessions a couple days ago, I presented a
> bunch of benchmark results comparing performance with different data/WAL
> block size. Most of the OLTP results showed significant gains (up to 50%) with
> smaller (4k) data pages.
Nice. I just saw th
On Thu, May 26, 2022 at 11:43 AM Masahiko Sawada wrote:
> Another idea I came up with is that we can wait for all index vacuums
> to finish while checking and updating the progress information, and
> then calls WaitForParallelWorkersToFinish after confirming all index
> status became COMPLETED. Th
On Thu, Jun 2, 2022 at 6:37 PM Mary Xu wrote:
> I was using an object access hook for oat_post_create access while creating
> an extension and expected that I would be able to query for the newly created
> extension with get_extension_oid(), but it was returning InvalidOid. However,
> the same
On 6/6/22 16:27, Jakub Wartak wrote:
> Hi Tomas,
>
>> Hi,
>>
>> At on of the pgcon unconference sessions a couple days ago, I presented a
>> bunch of benchmark results comparing performance with different data/WAL
>> block size. Most of the OLTP results showed significant gains (up to 50%)
>> w
Hi Thomas,
Correct. We're running with disabled parallel leader participation and we
have to do so, because another custom plan node we built relies on that.
That would be great. Anything else I can help with to get this patch in?
Thanks!
--
David
(ServiceNow)
On Fri, 3 Jun 2022 at 00:06, Thoma
On Fri, Jun 3, 2022 at 7:36 PM Michael Paquier wrote:
>
> On Fri, Jun 03, 2022 at 10:04:12AM -0400, Tom Lane wrote:
> > I agree with Robert's complaint that Parallel is far too generic
> > a term here. Also, the fact that this data is currently in struct
> > Port seems like an artifact.
> >
> > D
On 6/6/22 17:00, Tomas Vondra wrote:
>
> On 6/6/22 16:27, Jakub Wartak wrote:
>> Hi Tomas,
>>
>>> Hi,
>>>
>>> At on of the pgcon unconference sessions a couple days ago, I presented a
>>> bunch of benchmark results comparing performance with different data/WAL
>>> block size. Most of the OLTP r
Justin Pryzby writes:
> I noticed this is showing "pre-computed" gucs, like:
> shared_memory_size| 149MB
> shared_memory_size_in_huge_pages | 75
> I'm not opposed to that, but I wonder if that's what's intended / best.
I had suggested upthread that we might want to hide items w
> On 6 Jun 2022, at 15:30, Dong Wook Lee wrote:
> I just wrote a test code for the `pg_buffercache` extension which
> doesn't not have test code.
Please add this patch to the next commitfest to make sure it's not lost before
then.
https://commitfest.postgresql.org/38/
--
Daniel Gustafs
Dear Justin,
Thank you for your quick reply.
Unfortunately, the server having this issue is an Azure Flexible Server.
Upgrades are managed by Azure, I will have to wait until they release the
version 13.7.
Is there a procedure to replicate the database and preserve the bug.
My attempts with pg_d
On Mon, Jun 6, 2022 at 12:02 PM Tom Lane wrote:
> Thoughts?
This all seems pretty subjective. As someone who sometimes supports
customers, I usually kind of want the customer to give me all the
settings, just in case something that didn't seem important to them
(or to whoever coded up the \dconfi
Greetings,
* Daniel Gustafsson (dan...@yesql.se) wrote:
> > On 6 Jun 2022, at 15:30, Dong Wook Lee wrote:
>
> > I just wrote a test code for the `pg_buffercache` extension which
> > doesn't not have test code.
>
> Please add this patch to the next commitfest to make sure it's not lost before
>
> On Jun 6, 2022, at 9:02 AM, Tom Lane wrote:
>
> Thoughts?
I think it depends on your mental model of what \dconfig is showing you. Is it
showing you the list of configs that you can SET, or just the list of all
configs?
Dagfinn Ilmari Mannsåker writes:
> Hi hackers,
>
> Inspired by a question on IRC, I noticed that while the core statement
> logging system gained the option to log statement parameters in PG 13,
> auto_explain was left out.
>
> Here's a patch that adds a corresponding
> auto_explain.log_parameter
On Mon, 2022-06-06 at 10:51 -0400, Robert Haas wrote:
> I don't think a proposal to add CommandCounterIncrement() calls just
> for the convenience of object access hooks has much chance of being
> accepted.
Out of curiosity, why not? The proposed patch only runs it if the
object access hook is set
> On 6 Jun 2022, at 06:17, Michael Paquier wrote:
> On Mon, Jun 06, 2022 at 02:38:03AM +0200, Daniel Gustafsson wrote:
>> On 5 Jun 2022, at 11:19, Michael Paquier wrote:
>>> I have been toying with the idea of a sub-directory named with a
>>> timestamp (Unix time, like log_line_prefix's %n but t
On Mon, Jun 6, 2022 at 1:35 PM Jeff Davis wrote:
> Out of curiosity, why not? The proposed patch only runs it if the
> object access hook is set. Do you see a situation where it would be
> confusing that an earlier DDL change is visible? And if so, would it
> make more sense to call CCI unconditio
On Fri, Jun 3, 2022 at 10:04 AM Tom Lane wrote:
> I agree with Robert's complaint that Parallel is far too generic
> a term here. Also, the fact that this data is currently in struct
> Port seems like an artifact.
Why do we call this thing a Port, anyway?
I think I'd feel more comfortable here
Greetings,
* Andres Freund (and...@anarazel.de) wrote:
> On 2022-06-02 19:30:16 -0700, Andres Freund wrote:
> > On 2021-03-16 18:48:08 +, Stephen Frost wrote:
> > > Use pre-fetching for ANALYZE
> > >
> > > When we have posix_fadvise() available, we can improve the performance
> > > of an ANAL
On Mon, Jun 06, 2022 at 07:43:53PM +0200, Daniel Gustafsson wrote:
> > On 6 Jun 2022, at 06:17, Michael Paquier wrote:
> > On Mon, Jun 06, 2022 at 02:38:03AM +0200, Daniel Gustafsson wrote:
> >> On 5 Jun 2022, at 11:19, Michael Paquier wrote:
>
> >>> I have been toying with the idea of a sub-dir
On Mon, Jun 06, 2022 at 04:50:55PM +, Jean Landercy - BEEODIVERSITY wrote:
> Dear Justin,
>
> Thank you for your quick reply.
> Unfortunately, the server having this issue is an Azure Flexible Server.
> Upgrades are managed by Azure, I will have to wait until they release the
> version 13.7.
On Thu, Jun 2, 2022 at 12:26 PM Robert Haas wrote:
> 1. Extend the GRANT role_name TO role_name [ WITH ADMIN OPTION ] with
> a new, optional clause, something like WITH NO INHERIT or WITH
> NOINHERIT or WITHOUT INHERIT.
I just realized that, with ADMIN OPTION, you can change your mind
after the i
On Mon, 2022-06-06 at 13:43 -0400, Robert Haas wrote:
> Yeah, that comment could be made more clear.
I still don't understand what the rule is.
Is the rule that OAT_POST_CREATE must always use SnapshotSelf for any
catalog access? And if so, do we need to update code in contrib
extensions to follo
On Mon, Jun 6, 2022 at 3:46 PM Jeff Davis wrote:
> On Mon, 2022-06-06 at 13:43 -0400, Robert Haas wrote:
> > Yeah, that comment could be made more clear.
>
> I still don't understand what the rule is.
>
> Is the rule that OAT_POST_CREATE must always use SnapshotSelf for any
> catalog access? And i
Hello Tomas,
At on of the pgcon unconference sessions a couple days ago, I presented
a bunch of benchmark results comparing performance with different
data/WAL block size. Most of the OLTP results showed significant gains
(up to 50%) with smaller (4k) data pages.
You wrote something about SS
Robert Haas writes:
> I think part of the problem here, though, is that one can imagine a
> variety of charters that might be useful. A user could want to see the
> parameters that have values in their session that differ from the
> system defaults, or parameters that have values which differ from
Robert Haas writes:
> On Mon, Jun 6, 2022 at 1:35 PM Jeff Davis wrote:
>> Out of curiosity, why not? The proposed patch only runs it if the
>> object access hook is set. Do you see a situation where it would be
>> confusing that an earlier DDL change is visible? And if so, would it
>> make more s
On Mon, 6 Jun 2022 at 21:34, Jean Landercy - BEEODIVERSITY
wrote:
> SELECT COUNT(*) FROM items;
> -- ERROR: variable not found in subplan target list
> -- SQL state: XX000
Can you share some more details about what "items" is. psql's "\d
items" output would be useful. From what you've reported
On Sun, 5 Jun 2022 at 11:23, Tomas Vondra wrote:
> At on of the pgcon unconference sessions a couple days ago, I presented
> a bunch of benchmark results comparing performance with different
> data/WAL block size. Most of the OLTP results showed significant gains
> (up to 50%) with smaller (4k) da
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Mon, Feb 7, 2022 at 11:13 AM Joe Conway wrote:
> > > It seems to me that the INHERIT role flag isn't very well-considered.
> > > Inheritance, or the lack of it, ought to be decided separately for
> > > each inherited role. However, that
On Mon, Jun 06, 2022 at 01:53:35PM -0500, Justin Pryzby wrote:
> It seems important to use a format in most-significant-parts-first which sorts
> nicely by filename, but otherwise anything could be okay.
Agreed.
> Apparently, that's ISO 8601, which can optionally use separators
> (-MM-DDTHH:M
On Mon, 6 Jun 2022 at 07:28, Ranier Vilela wrote:
> 4) 004-generation-reduces-memory-consumption-BUG.patch
> Same to the (2), but with BUG.
> It only takes a few tweaks to completely remove the field block.
> This fails with make check.
> I couldn't figure out why it doesn't work with 16 bits (st
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Thu, Jun 2, 2022 at 3:51 PM Tom Lane wrote:
> > > I sort of thought http://postgr.es/m/3981966.1646429...@sss.pgh.pa.us
> > > constituted a completed investigation of this sort. No?
> >
> > I didn't think so. It's clear that the spec e
Em seg., 6 de jun. de 2022 às 20:37, David Rowley
escreveu:
> On Mon, 6 Jun 2022 at 07:28, Ranier Vilela wrote:
> > 4) 004-generation-reduces-memory-consumption-BUG.patch
> > Same to the (2), but with BUG.
> > It only takes a few tweaks to completely remove the field block.
>
> > This fails with
Jim Nasby writes:
>> I think the real problem here is that the underlying software mostly
>> doesn't take this issue seriously.
> The first step to a solution is admitting that the problem exists.
> Ignoring broken backups, segfaults and data corruption as a "rant"
> implies that we simply thro
> On Jun 6, 2022, at 17:10, Jim Nasby wrote:
> Ignoring broken backups, segfaults and data corruption as a "rant" implies
> that we simply throw in the towel and tell users to suck it up or switch
> engines.
Well now, let’s be clear, I was the one who called my email a “rant”. 🙂
And I do
On Tue, Jun 7, 2022 at 12:10 PM Jim Nasby wrote:
> On 6/3/22 3:58 PM, Tom Lane wrote
> > Thomas Munro writes:
> >> On Sat, Jun 4, 2022 at 7:13 AM Jeremy Schneider
> >> wrote:
> >>> It feels to me like we're still not really thinking clearly about this
> >>> within the PG community, and that the
Em seg., 6 de jun. de 2022 às 21:14, Ranier Vilela
escreveu:
> Em seg., 6 de jun. de 2022 às 20:37, David Rowley
> escreveu:
>
>> On Mon, 6 Jun 2022 at 07:28, Ranier Vilela wrote:
>> > 4) 004-generation-reduces-memory-consumption-BUG.patch
>> > Same to the (2), but with BUG.
>> > It only takes
I removed it on your advice.
Thanks.
2022년 6월 7일 (화) 오전 2:04, Stephen Frost 님이 작성:
>
> Greetings,
>
> * Daniel Gustafsson (dan...@yesql.se) wrote:
> > > On 6 Jun 2022, at 15:30, Dong Wook Lee wrote:
> >
> > > I just wrote a test code for the `pg_buffercache` extension which
> > > doesn't not have
On Tue, Jun 07, 2022 at 08:30:47AM +0900, Michael Paquier wrote:
> If we don't split by the millisecond, we would come back to the
> problems of the original report. On my laptop, the --check phase
> that passes takes more than 1s, but the one that fails takes 0.1s, so
> a follow-up run would comp
On Sat, 2022-06-04 at 21:18 +, Phil Florent wrote:
> I opened an issue with an attached code on oracle_fdw git page :
> https://github.com/laurenz/oracle_fdw/issues/534
> Basically I expected to obtain a "no privilege" error from PostgreSQL when I
> have no read privilege
> on the postgres f
tather => rather
is charge => in charge
On Mon, Jun 06, 2022 at 01:17:52PM +0900, Michael Paquier wrote:
> but something like %Y%m%d_%H%M%S.%03d (3-digit ms for last part) would
On Tue, Jun 07, 2022 at 08:30:47AM +0900, Michael Paquier wrote:
> I would reduce the format to be MMDDTHHMMSS_ms (
On Mon, May 9, 2022 at 7:07 PM Pavel Stehule wrote:
> út 13. 7. 2021 v 19:50 odesílatel Tom Lane napsal:
>> ^Cregression=#
>>
>> then as you can see I get nothing but the "^C" echo before the next
>> psql prompt. The problem with this is that now libreadline is
>> misinformed about the cursor po
Thomas Munro writes:
> On Mon, May 9, 2022 at 7:07 PM Pavel Stehule wrote:
>> út 13. 7. 2021 v 19:50 odesílatel Tom Lane napsal:
>>> ^C\watch cancelled
>>> regression=#
> Do we really need the extra text? What about just \n, so you get:
> postgres=# \watch 1
> ...blah blah...
> ^C
> postgres=
At Mon, 6 Jun 2022 08:32:01 -0400, James Coleman wrote in
> On Mon, Jun 6, 2022 at 1:26 AM Kyotaro Horiguchi
> wrote:
> >
> > At Sat, 4 Jun 2022 19:09:41 +0530, Bharath Rupireddy
> > wrote in
> > > On Sat, Jun 4, 2022 at 6:29 PM James Coleman wrote:
> > > >
> > > > A few weeks back I sent a b
The logical replication tablesync ignores the publication 'publish'
operations during the initial data copy.
This is current/known PG behaviour (e.g. as recently mentioned [1])
but it was not documented anywhere.
This patch just documents the existing behaviour and gives some examples.
--
[1
On Tue, Jun 7, 2022 at 3:23 PM Tom Lane wrote:
> The code needs a comment about why it's emitting a newline, though.
> In particular, it had better explain why that should be conditional
> on !pagerpipe, because that makes no sense to me.
Yeah. OK, here's my take:
+ /*
+
út 7. 6. 2022 v 6:50 odesílatel Thomas Munro
napsal:
> On Tue, Jun 7, 2022 at 3:23 PM Tom Lane wrote:
> > The code needs a comment about why it's emitting a newline, though.
> > In particular, it had better explain why that should be conditional
> > on !pagerpipe, because that makes no sense to
I've been doing some preliminary prep work to see how an inverted index
using roaring bitmaps (https://roaringbitmap.org/) would perform. I'm
presenting some early work using SQL code with the roaring bitmap Postgres
extension (https://github.com/ChenHuajun/pg_roaringbitmap) to simulate a
hypotheti
61 matches
Mail list logo
