caching in the index. *Unless you can *guarantee* that data is
entered in perfect order, and/or never changes, I don't think what I'm
looking for is likely to make sense.
On Fri, Apr 5, 2024 at 11:27 AM Morris de Oryx
wrote:
> Looking for an index to support top-n searches, wer
Looking for an index to support top-n searches, were n has a fixed maximum
Recently, I've been looking at strategies to handle top-n queries in
Postgres. In my current cases, we've got definition tables, and very large
related tables. Here's a stripped-down example, the real tables are much
wider.
>
>
> I think you're overthinking it.
>
*Moi*? Never happens ;-)
Fantastic answer, thanks very much for giving me all of these details.
Coming from you, I'll take it as authoritative and run with it.
I've got a small question about marking functions working with decimal
number types as either IMMUTABLE or STABLE. Below are a pair of trivial
functions that show what I'm guessing. An int8/int8[] seems like it's going
to be immutable forever. However, decimal types aren't quite so crisp and
consis
Thanks or the confirmation, and here's hoping no ICBMs!
n thinking that this patch will be integrated into 14.9/15.4,
if they are released?
Thank you
On Mon, Jun 5, 2023 at 6:20 PM Morris de Oryx
wrote:
> Reminds me to say a *big* *thank you* to everyone involved in and
> contributing to Postgres development for making error messages which are s
Another suggestion for AWS/RDS: Expose *all of the logs in the upgrade tool
chain*. If I'd had all of the logs at the start of this, I'd have been able
to track down the issue myself quite quickly. Setting up that simple case
database took me less than an hour today. Without the logs, it's been
imp
they alway seem to be *on topic*, and enough to get you on the right
track.I assume that we've all used programs and operating systems that emit
morerunic...errors.
On Mon, Jun 5, 2023 at 6:03 PM Morris de Oryx
wrote:
> Another suggestion for AWS/RDS: Expose *all of the logs in the u
Well *that *was quick. Thank you!
Imseih, Sami what are the chances of getting RDS to apply this patch?
Postgres 15 was released nearly 8 months ago, and it would be great to get
onto it.
Thanks
On Mon, Jun 5, 2023 at 3:01 PM Tom Lane wrote:
> Morris de Oryx writes:
> > Can anyone
Edit error above, I said that dependency tracking "does not seem to work."
Not what I mean, it works great...It just does not seem to work for me with
any of the upgrade options.
>
Thanks to Imseih and Sami at AWS for reporting this. The original case
comes from an upgrade I've been trying to complete for a couple of months
now, since RDS started supporting 15 with a 15.2 release.
The process has been slow and painful because, originally, there was a bug
on the RDS side that
On Tue, Jul 19, 2022 at 10:38 PM Robert Haas wrote:
> For MERGE itself, I wonder if some information about this should be
> included in the command tag. It looks like MERGE already includes some
> sort of row count in the command tag, but I guess perhaps it doesn't
> distinguish between inserts
y
necessary.
Sounds like a lot of work for not much gain, at least in this narrow case.
Thanks again for answering.
On Tue, Jul 19, 2022 at 6:43 PM Morris de Oryx
wrote:
> > What is motivating you to want to see the xmax value here? It's not an
> > unreasonable thing to want
lient result.
It's fine. A rich result summary would be very nice. As in rows
added/modified/deleted on whatever table(s). If anyone ever decides to
implement such a structure for MERGE, it would be nice to see it
retrofitted to the other data modification commands where RETURNING wo
I've run into an existing behavior where xmax(), and various other system
tables, return an error when included in the RETURNING list on a
partitioned table.
ERROR: cannot retrieve a system column in this context
`
This issue got a fair airing back in 2020:
AW: posgres 12 bug (partitioned table)
ction.
All the same, I've learned a _lot_ of important points about Postgres from
trying to sort all of this out. Your messages have been a real help.
On Tue, Jul 16, 2019 at 7:03 PM Adrien Nayrat
wrote:
> On 7/12/19 2:50 PM, Morris de Oryx wrote:
> > Adrien, thanks very much for
Adrien, thanks very much for answering my question. Just a couple of
follow-up points, if you don't mind.
In our answer, you offer an example of pg_xact_commit_timestamp showing
out-of-sequence commit times:
Session xid pg_xact_commit_timestamp
A 34386826 2019-07-11 09:
I have some specific questions about pg_xact_commit_timestamp, and am
hoping that this is the right place to ask. I read a lot of the commentary
about the original patch, and the contributors seem to be here. If I'm
asking in the wrong place, just let me know.
I'm working on a design for a concurr
Hello, I'm not a C coder and can't helpbut I *love* cross-tab/pivot
tables. They're the best, and just fantastic for preparing data to feed
into various analysis tools. The tablefunc module is helpful, but a bit
awkward to use (as I remember it.)
>From a user's point of view, I high-performanc
19 matches
Mail list logo
