Jeff Janes writes:
> On Mon, Jan 22, 2018 at 9:16 AM, Tom Lane wrote:
>> The point here is that that's an uncorrelated subselect --- ie, it
>> contains no outer references --- so it need not be, and is not,
>> re-evaluated at every outer row.
> That seems rath
won't
be cheap though. There's definitely no easy, certain-to-work answer.
regards, tom lane
ion is installed in a schema
that isn't in your search_path.
regards, tom lane
havior in this area come up, they
get batted down.
What we do have though is client-side support for appropriate behaviors.
In psql, see the AUTOCOMMIT and ON_ERROR_ROLLBACK control variables.
Other interfaces such as JDBC have their own ideas about how this ought
to work.
regards, tom lane
"David G. Johnston" writes:
> On Mon, Jan 29, 2018 at 8:33 AM, Tom Lane wrote:
>> What we do have though is client-side support for appropriate behaviors.
>> In psql, see the AUTOCOMMIT and ON_ERROR_ROLLBACK control variables.
> Not quite the same. I think what peop
Vitaliy Garnashevich writes:
> But what is "dirtied" statistics? When a SELECT query could make pages
> dirty?
Setting hint bits on recently-committed rows.
regards, tom lane
behind
to combine additional condition(s) with a basic character-class pattern.
Something like
(?=[\001-\377])[^A-Za-z0-9%_]
regards, tom lane
t building that contrib
module against some other implementations; but there are still going to
be systems on which installing uuid-ossp is inconvenient.
There may also be a belief that pgcrypto's result is more
cryptographically secure, though I wouldn't swear to that.
regards, tom lane
issues of assorted severities.
For reference, the current latest minor releases are 10.2, 9.6.7, 9.5.11,
9.4.16, 9.3.21 (all newly minted today, as it happens). The 9.0.x and
8.x.x release branches have been out of support for years.
regards, tom lane
package it as one.)
regards, tom lane
Andres Freund writes:
> On February 11, 2018 2:48:13 PM PST, Tom Lane wrote:
>> (Any such patch should manage
>> to turn COPY-CSV into an extension, at least so far as copy.c is
>> concerned, even if we don't package it as one.)
> Yea, I was thinking we should
uot;Almost" because there'd need to be a way for it to
support the appropriate options. So this means that whatever the
mechanism is for extension-specific options, it has to be introspectable
enough for file_fdw.c to understand what to expose as FDW options.
regards, tom lane
there for a
very long time; we don't like to break plausible client queries lightly.
regards, tom lane
rograms.
Putting two and two together, you have some monitoring program that is
hitting the postmaster with a constant stream of TCP connection requests
none of which get completed, resulting in a whole lot of useless fork
activity. Dial down the monitoring.
regards, tom lane
Francisco Olarte writes:
> On Tue, Feb 13, 2018 at 4:50 PM, Tom Lane wrote:
>> Putting two and two together, you have some monitoring program that is
>> hitting the postmaster with a constant stream of TCP connection requests
>> none of which get completed, resulting in a
process inherits its
title from the parent at fork(), and per this discussion, they haven't
changed it yet.
regards, tom lane
f us rely on in practice.)
MariaDB has a much laxer notion of what compliance to the standard means
here, and AFAIK they feel free to add columns that are not in the
standard. We do not do that.
regards, tom lane
yet.
I'm not sure if you could identify a table rename without resorting to
writing some C code.
regards, tom lane
initial
state of an object typically includes some positive grants doesn't change
the fact that there's no such thing as a negative grant. In particular,
if there is a GRANT TO PUBLIC, no amount of revoking that privilege from
individual users will have any effect, because the public grant is still
there.
regards, tom lane
y of this sort ... but it's only test code and doesn't
necessarily have anybody's blessing as to being a good basis for moving
forward.
regards, tom lane
onstitute an improvement --- what do you wish it would
show you, exactly? In the particular case here, the fact that a varchar
length coercion is being invoked isn't even explicit in the query.
Good ideas welcome ...
regards, tom lane
across a crude POC hack here:
https://www.postgresql.org/message-id/21693.1478376...@sss.pgh.pa.us
At the time I didn't want to pursue it further because of Andres'
pending work on redoing expression execution, but that's landed now.
regards, tom lane
n order to figure out what your one or two
sentences are in response to.
Gmail have done their level best to destroy email in general, and mailing
lists in particular, as a useful communication medium. Don't help them
out by being a jerk about your quoting habits.
regards, tom lane
enerically applicable. In principle we could make it
work for any error arising during expression evaluation.
regards, tom lane
y needs to
figure out what's the approved way now to get the locale name out of a
_locale_t object.
regards, tom lane
stgres 127 Feb 19 12:27 Zulu
-rw-r--r--. 3 postgres postgres 3545 Feb 19 12:27 posixrules
regards, tom lane
next VS
update.
regards, tom lane
27;select $1[1]' language sql;
CREATE FUNCTION
regression=# select foo(array[1.1,1.2]);
foo
-
1.1
(1 row)
or to emphasize that it is doing a conversion:
regression=# select foo(array[1.1,1.2]::numeric[]);
foo
-
1.1
(1 row)
regards, tom lane
don't see any advantage there.
I don't see any point in making base/ be its own mount point. Once
you get rid of those other subdirectories there's not going to be
enough "global" storage left to justify its own volume.
regards, tom lane
ng tree entirely. But this sure
sounds reminiscent of that class of problems.
regards, tom lane
Ron Johnson writes:
> On 02/21/2018 06:01 PM, Tom Lane wrote:
>> Ron Johnson writes:
>>> Apparently, initdb assumes that data/ is one big mount point. However, we
>>> have four mount points:
>>> /var/lib/pgsql/9.6/data/backup
>>> /var/lib/pgsql/9.6
Lucas Fairchild-Madar writes:
> On Wed, Feb 21, 2018 at 4:14 PM, Tom Lane wrote:
>> If so, this might be some manifestation of a problem we've seen before:
>> the planner tries to find out the current live max value of the column
>> by scanning the index, and that&#x
member-what grounds.
But I couldn't find any such discussion in a quick trawl of the archives,
so maybe I'm misremembering. The only reasonable counter-argument I can
think of now is that it'd make the display Even Wider ... but \df+ long
since blew past any reasonable screen width.
regards, tom lane
then work with float8 and let
the implicit-coercion machinery do the conversion for you.
regards, tom lane
s.mk; maybe it's an ordering problem?
regards, tom lane
subpackage. Maybe you didn't
install that?
regards, tom lane
Karsten Hilbert writes:
> On Mon, Jan 29, 2018 at 03:57:48AM +0100, David Fetter wrote:
>> Tom Lane pushed:
>> ... This leaves us with no solution for the
>> default_transaction_read_only issue that commit 4bd371f6f intended to work
>> around, other than "you g
a foreign server that is more recent? Like
> pg14 connecting to pg17?
I'd expect it to work, but it's not a scenario that we test.
regards, tom lane
thing else
using the switch Adrian mentioned --- but that's really mostly
cosmetic. It has nothing to do with OS-level privileges.
regards, tom lane
KIM-verifying recipient would regard the
message as a forgery.
regards, tom lane
Christophe Pettus writes:
> On Oct 4, 2024, at 12:05, Tom Lane wrote:
>> Yeah, that's what it looks like. I'm a bit confused though because
>> 16.x should have failed the same way: building our docs without local
>> DTDs has failed for well over a year now [1].
a bit confused though because
16.x should have failed the same way: building our docs without local
DTDs has failed for well over a year now [1]. Perhaps you weren't
trying to build the docs before?
regards, tom lane
[1] https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=969509c3f
de of Postgres' control --- I don't think that libpq
itself has much involvement in the KDC communication.
I concur with looking at the Discourse release notes and maybe asking
some questions in that community.
regards, tom lane
uppet recipe is revoking that behind your
back, or if you are using some modified version of Postgres
with different ideas about default privileges. Looking at
psql \l output for the test DB might be informative.
regards, tom lane
er
one wouldn't necessarily please everybody.
regards, tom lane
ybe we could have
some guarantees about what you get when comparing other sessions'
xact_start to your own snapshot_timestamp. But I'm not convinced we
can really guarantee anything without reading the snapshot_timestamp
within the snapshot-collecting critical section, and I'm not for that.
regards, tom lane
27;s
a giant patch with a much smaller patch struggling to get out.
But certainly the area needs some nontrivial thought, and I'm not
sure that extending the GUC mechanism is a better answer.
regards, tom lane
[1]
https://www.postgresql.org/message-id/flat/CAFj8pRD053CY_N4%3D6SvPe7ke6xPbh%3DK50LUAOwjC3jm8Me9Obg%40mail.gmail.com
artly a
matter of not having a protocol spec that would allow the EXPLAIN data
to be delivered on a side channel, but mostly a recognition that
rewriting applications to capture such data would be painful.
regards, tom lane
emory serves. On a Linux box it seems
to work for processes owned by yourself even if you're not superuser.
regards, tom lane
fully
as you guard the database contents.
regards, tom lane
out
> recompilation.
I'm pretty down on this idea because it adds complexity, ie ways to
break things. If you want a more self-contained installation, you
could build it without specifying --with-system-tzdata.
regards, tom lane
utilities
like date(1).
regards, tom lane
Michel Pelletier writes:
> On Sun, Oct 20, 2024 at 10:13 AM Tom Lane wrote:
>> But it seems like we could get an easy win by adjusting
>> plpgsql_exec_function along the lines of
>> ...
> I tried this change and couldn't get it to work, on the next line:
> if
Michel Pelletier writes:
> I found this thread from the original path implementation from Tom Lane in
> 2015:
> https://www.postgresql.org/message-id/E1Ysvgz-s0-DP%40gemulon.postgresql.org
>> In this initial implementation, a few heuristics have been hard-wired
>> in
src/backend/Makefile ... they don't look that easy to mess up,
but maybe.
regards, tom lane
Which is how come no other
program responds to that environment variable. So if anything, that's
precedent for our behavior.
regards, tom lane
Michel Pelletier writes:
> On Sun, Oct 20, 2024 at 10:13 AM Tom Lane wrote:
>> The other problem is that plpgsql only knows how to do such expansion
>> for arrays, and it's not obvious how to extend that part.
> Perhaps a third member function for ExpandedObjectMethod
n probes.d don't entirely match up with the calls
in the source code. You could compare the relevant bits of code
between vanilla and modified 16.4 if the problem isn't immediately
obvious.
regards, tom lane
o a lower-bound date somewhere
around 30 BC. If you need to deal with geological or astronomical
time spans, then yeah you need a new type --- but presumably you would
not feel a need to tie it to Gregorian calendar dates, so the need to
reimplement a ton of related logic would not be there.
as usual, but it doesn't look like there's any case where
they are more permissive than the Linux rule. I'm still not convinced
about whether all *BSD flavors match that, though.
regards, tom lane
Achilleas Mantzios writes:
> Στις 16/10/24 19:47, ο/η Tom Lane έγραψε:
>> I believe it depends on your platform --- some BSDen are pretty
>> permissive about this, if memory serves. On a Linux box it seems
> As of FreeBSD smadevnu 14.1-RELEASE-p5 , only the user and root c
ome bizarre syntax that we couldn't parse without making JSON
a partially-reserved word. It still works as a type name, but
in this particular syntax where it's not initially clear which
names are type names, you lose. Double-quote the argument name,
or name it something other than "json".
regards, tom lane
It was awhile ago though.
It might be worth searching our mailing list archives.
regards, tom lane
NOT DISTINCT FROM predicates not being efficient,
so the benefits would be wider than just INTERSECT.
regards, tom lane
;ll get N copies of it, which I assume is not what you want.
Better
regression=# select f1 from zed order by f1 offset 4 limit 1;
f1
5
(1 row)
which gets you just the one row and is a lot cheaper too.
regards, tom lane
ered but indicate to the reader that the column applies to *my
> copy* but are not columns in the original data.
Of course, if they decide to name something "_foo", you're going to
need to figure out what to do with that.
regards, tom lane
Dominique Devienne writes:
> On Tue, Nov 5, 2024 at 6:42 PM Tom Lane wrote:
>> This is probably a bug, at least to the extent that we don't like
>> XX000 errors to be easily reachable, so please let us know what
>> you find out.
> Finding where the error is thrown
o please let us know what
you find out.
regards, tom lane
David Rowley writes:
> On Tue, 5 Nov 2024 at 04:18, Tom Lane wrote:
>> A different idea that occurred to me while looking at this is:
>> why have we got all this machinery to add and check a flag
>> column, rather than arranging things so that the two input
>> relat
regards, tom lane
emplate0;
CREATE DATABASE
or
regression=# create database db2 with encoding = 'utf8' icu_locale =
'en-US-x-icu' locale_provider = icu template = template0;
CREATE DATABASE
or
regression=# create database db3 with encoding = 'utf8' locale = 'POSIX'
template = template0;
CREATE DATABASE
regards, tom lane
t be what Alvaro was muttering about
the other day: redesign FKs for partitioned tables so that we
do not have to change the set of triggers when attaching/detaching.
regards, tom lane
current_user.
Worse than that: what it reports is libpq's PQuser(), that is the
name that was used to log in with. But if what you want is the
session_user, psql prompts already have %n for that.
regards, tom lane
il.com
At the time I didn't like the idea too much, but now that we've seen
a second independent request, maybe our opinion of its value should
go up a notch.
regards, tom lane
d that hugely compelling, because there's always going
to be some skew between the time we read the clock for the timestamp
and the time we obtain the snapshot. Admittedly, that would normally
not be a very long interval if BEGIN did both things ... but on a
busy system you could lose the CPU for awhile in between.
regards, tom lane
orting failures like this. It looks to me like there is something
wrong with your libicu installation --- perhaps headers out of sync
with shared library?
regards, tom lane
s is important in some scenarios.
regards, tom lane
in the first place. If that's what you
want, don't partition your table.
regards, tom lane
concurrently, this needn't involve
much downtime.
regards, tom lane
lying
table engine, meaning that what we know about performance may not
be terribly relevant.
regards, tom lane
a race condition it might look more like "duplicate key value
violates unique constraint". In the end we rely on the system
catalogs' unique indexes to detect and prevent race conditions of
this sort.
regards, tom lane
#x27;USAGE WITH ADMIN OPTION' seems a reasonable choice.
regards, tom lane
I'm now inclined to add wording within the pg_has_role entry, along
the lines of
WITH ADMIN OPTION or WITH GRANT OPTION can be added to any of
these privilege types to test whether ADMIN privilege is held
(all six spellings test the same thing).
regards, tom lane
ently across transactions
(eg, sort by primary key before inserting)?
regards, tom lane
Robert Haas writes:
> On Fri, Sep 20, 2024 at 2:34 PM Tom Lane wrote:
>> I'm now inclined to add wording within the pg_has_role entry, along
>> the lines of
>>
>> WITH ADMIN OPTION or WITH GRANT OPTION can be added to any of
>> these privilege types t
u ought to think about while you're at it.
If there are any other old-style extensions in there, better
fix them up.
regards, tom lane
LE AS, that I/O would be extra.
regards, tom lane
able to reindex indexes on string columns.
regards, tom lane
. If it says SELECT, it gets a snapshot.
regards, tom lane
I wrote:
> Thanks for the test case! A quick "git bisect" says I broke it at
> cb8e50a4a09fe541e32cd54ea90a97f2924121a1 is the first bad commit
> commit cb8e50a4a09fe541e32cd54ea90a97f2924121a1
> Author: Tom Lane
> Date: Fri Aug 30 12:42:12 2024 -0400
> Avoid
Paul Foerster writes:
> On 26 Nov 2024, at 22:25, Tom Lane wrote:
>> I'm suspicious that our repair recipe might not have accounted
>> for self-reference FKs fully, but that's just a gut feeling at
>> this point.
> Of course, it contains no secret da
g/wiki/Guide_to_reporting_problems
regards, tom lane
ad commit
commit cb8e50a4a09fe541e32cd54ea90a97f2924121a1
Author: Tom Lane
Date: Fri Aug 30 12:42:12 2024 -0400
Avoid inserting PlaceHolderVars in cases where pre-v16 PG did not.
Apparently that change was less safe than I thought. Looking ...
regards, tom lane
d 7.0
(whenever we introduced the version-3 wire protocol). We don't
routinely test it against anything older than 9.2, but I tried
current psql against 8.2 (the oldest functional server I have
on this machine) and it basically worked.
regards, tom lane
error
message implies that something is still holding a reference count
on "a"'s relcache entry, and it's hard to see what that could be
except a still-open Portal for the SELECT.
regards, tom lane
onstraint.
> The release notes say nothing about when to fix that using the generated add
> or drop statements.
Generally speaking, our release notes are addressed to someone who's
already installed the update (or a later one).
regards, tom lane
out it?
Batch the DB updates, perhaps?
> What's interesting it happens only if the function called by plpyhon makes
> changes to DB.
Totally unsurprising. XIDs are acquired only when the current
transaction or subtransaction first needs to change the DB.
regards, tom lane
design for what should happen and a patch
implementing that, we've just left it at the status quo, which is that
Params are only available to the DML statements Achilleas mentioned.
regards, tom lane
that matter also for p_ci_pipelines?
Did the FK used to reference the whole partitioned table, or just
this partition?
I'm suspicious that our repair recipe might not have accounted
for self-reference FKs fully, but that's just a gut feeling at
this point.
regards, tom lane
work afoot to fix
that [1], but it's not committed yet let alone in any shipping
version. Nonetheless, your best bet for fixing this might be
to install the earthdistance 1.2 files from the latest patchset in
that thread.
regards, tom lane
[1] https://www.postg
2701 - 2800 of 2962 matches
Mail list logo
