On 06.06.25 17:46, Jacob Champion wrote:
On Fri, Jun 6, 2025 at 7:17 AM Tom Lane wrote:
Peter Eisentraut writes:
Since we now require Python 3.6, we can also remove PL/Python test
alternative expected files for earlier Python versions. See attached patch.
+1. So nice to get rid of src/pl/
Hello David,
24.12.2024 03:57, David Rowley wrote:
On Tue, 24 Dec 2024 at 11:19, David Rowley wrote:
The attached adjusts that Assert code so that a fresh CompactAttribute
is populated instead of modifying the TupleDesc's one. I'm not sure
if populate_compact_attribute_internal() is exactly th
Hi Masahiko,
On Sat, Jun 7, 2025 at 5:34 AM Masahiko Sawada wrote:
>
> On Tue, May 13, 2025 at 2:26 PM Matheus Alcantara
> wrote:
> >
> > Hi,
> >
> > On 30/04/25 19:36, Masahiko Sawada wrote:
> > > Here are the summary of each attached patch:
> > >
> > > 0001: Introduce TIdStoreIsMemberMulti() w
On Sat, Jun 7, 2025 at 8:46 PM Junwang Zhao wrote:
>
> Hi Masahiko,
>
> On Sat, Jun 7, 2025 at 5:34 AM Masahiko Sawada wrote:
> >
> > On Tue, May 13, 2025 at 2:26 PM Matheus Alcantara
> > wrote:
> > >
> > > Hi,
> > >
> > > On 30/04/25 19:36, Masahiko Sawada wrote:
> > > > Here are the summary of
On 06/06/2025 10:21 pm, Tom Lane wrote:
Konstantin Knizhnik writes:
There is really essential difference in code generated by clang 15
(working) and 16 (not working).
It's a mistake to think that this is a compiler bug. The C standard
explicitly allows compilers to use word-wide operations
On Fri, Jun 6, 2025 at 8:04 PM David Rowley wrote:
> On Fri, 6 Jun 2025 at 14:32, Robert Treat wrote:
> > In production, you aren't watching to see what happen with
> > pg_stat_all_indexes, because you will first be watching pg_stat_activity to
> > see if the plans have flipped in some way that
On Fri, Apr 11, 2025 at 5:28 PM Antonin Houska wrote:
>
> Please check the next version [1]. Thanks for your input.
>
> [1] https://www.postgresql.org/message-id/97795.1744363522%40localhost
>
Hi, I’ve briefly experimented with v13-0001.
EXPLAIN tab complete:
explain (verbose O
OFF ON
since we
On Thu, Jun 5, 2025 at 08:32:44PM -0400, Bruce Momjian wrote:
> On Wed, Jun 4, 2025 at 05:53:38PM -0400, Bruce Momjian wrote:
> > On Wed, Jun 4, 2025 at 02:29:46PM -0700, Noah Misch wrote:
> > > I agree with David G. Johnston's feedback on this. My draft didn't
> > > mention
> > > SECURITY DEF
> In that type of environment, the GUC-only method enables you to
> control changes at very precise levels, so you can do things like:
> - run it ad-hoc at the session level to confirm that the explain plans
> you get in production match your expectations.
> - you can stay ad-hoc at the session lev
Hi
only rebase
Regards
Pavel
From d589a48d746d05368ee49e6a1e0202da9b75b0f6 Mon Sep 17 00:00:00 2001
From: "ok...@github.com"
Date: Sun, 16 Jun 2024 15:52:38 +0200
Subject: [PATCH 3/3] set plpgsql.extra_errors to "none"
Purpose of previous commit was to run tests with active strict_expr_check.
Dear PostgreSQL Community,
I hope this message finds you well. I am writing to propose a set of
features aimed at significantly enhancing PostgreSQL’s management and
observability in cloud environments, particularly for administrators who do
not have direct access to the underlying operating system
Hi all,
I need to switch search_paths often. It would be tremendously helpful to
see the current search_path in the prompt.
-
Lauri Siltanen
On Sat, 7 Jun 2025 at 20:52, Lauri Siltanen wrote:
> I need to switch search_paths often. It would be tremendously helpful to see
> the current search_path in the prompt.
That feature should be pretty easy to implement, now that search_path
is marked as GUC_REPORT in PG18. Basically you need to
On Sun, 8 Jun 2025 at 01:35, Robert Treat wrote:
>
> On Fri, Jun 6, 2025 at 8:04 PM David Rowley wrote:
> > Can you list your proposed series of steps you'd recommend to a DBA
> > wishing to remove an index, assuming this feature exists in core as
> > you'd like it to?
> >
>
> Well, the series of
On Fri, 2025-06-06 at 09:08 +0530, sreekanta reddy 1996 wrote:
> I am writing to propose a set of features aimed at significantly enhancing
> PostgreSQL’s management and observability in cloud environments, particularly
> for administrators who do not have direct access to the underlying operating
Hi
I started reviewing this patch.
so 7. 6. 2025 v 18:41 odesílatel Tom Lane napsal:
> This is a rather delayed response to the discussion of bug
> #18693 [1], in which I wrote:
>
> > (It's kind of annoying that "strict" has to be double-quoted
> > in the RAISE NOTICE, especially since you get
16 matches
Mail list logo
