ems in the past that could
lead to unreasonable numbers of temp files in hash joins. Whether
there's more to do, or Peter is running a version that lacks those
fixes, is impossible to tell with the given info.)
regards, tom lane
hash batches needed, which likely plays into
this somehow.
regards, tom lane
ocess. Maybe
you are restoring the backup into a database that isn't empty,
but already contains the aspnet*.* tables?
regards, tom lane
aracters in your input file;
perhaps a control-D or ASCII NUL would produce that symptom.
regards, tom lane
[ please keep the list cc'd ]
JORGE MALDONADO writes:
> As for the answer by *Tom Lane*, I am not restoring the DB but only getting
> the backup in plain format. I see that tables that contain "AspNet" in
> their name are part of the resulting dumped file. For example, th
at would probably be reverse-engineering an
explanation. I think that "we didn't bother" is more nearly the
situation.
regards, tom lane
mal [1], so it's not a case of "it's completely
broken". But you need the appropriate prerequisites, eg
an Xcode installation [2]. I wonder exactly what configure
options the OP is using, and what's installed on his Mac
beyond bare macOS.
ourselves having to make those
keywords more reserved than they are now.
regards, tom lane
n disclaimer, I'm not too sad about it.
If somebody did want to relax this restriction, the thing to do would be
to remove the datum type limitation altogether, not just restore bug
compatibility with the old behavior.
regards, tom lane
ls down to one of getting
the quoting around the double-quoted pattern correct. I'm not a
Windows user so I don't know much about shell quoting rules there.
regards, tom lane
PI. I think it
could only work for a plan-time-constant range though, else you'd not know
whether to use equality or inequality bounds. (Hmm ... or maybe, use
equality always and treat it as a lossy conversion? But infinite bounds
would still be a headache.)
regards, tom lane
same installation instructions I pointed you to before:
https://www.postgresql.org/docs/13/installation.html
regards, tom lane
(There are some hacks involving
toplevel vs not-top-level Makefiles that you might be falling
foul of.)
regards, tom lane
s then a
likely explanation for the problem is lack of the "MAKELEVEL=0" bit.
regards, tom lane
psql command line. A very quick test
>> seems to indicate that you can.
> Nope. No difference.
Perhaps your psql is built against libedit rather than readline.
regards, tom lane
postgresql.git&a=commitdiff&h=ccd10a9bf
regards, tom lane
ent is trying to set the PG server's timezone setting or
not. Your issue may be purely a Python one.)
regards, tom lane
uot; to the client. And that's actually one of the harder
cases to deal with: if the connection drops just after you issue
COMMIT, you can't tell whether the transaction got committed.
regards, tom lane
#x27;t want to wait around for autovacuum to get to it.
regards, tom lane
7;2020701'::date;
^
psql (9.4.26)
Type "help" for help.
regression=# select '2020701'::date;
date
0202-07-01
(1 row)
If you want to pursue this question, you could start by bisecting
to find just which commit changed it and why.
regards, tom lane
"David G. Johnston" writes:
> On Monday, May 9, 2022, Tom Lane wrote:
>> If you want to pursue this question, you could start by bisecting
>> to find just which commit changed it and why.
> Manual history inspection of datetime.c
> https://gith
immediate" shutdown)
and then take the snapshot.
regards, tom lane
B to be able to share some data, you can probably build the connections
you need using foreign tables or logical replication; but there's not
a lot of pre-fab infrastructure for that, AFAIK.
regards, tom lane
(now() + '-7day')::date;
date
2022-05-10
(1 row)
You might also want to look at other non-text-based manipulations
such as date_trunc() and date_part().
regards, tom lane
's true that it's not very easy to tell where any given value
came from, but I doubt it'd be worth an ABI break to add such info.
(You could at least recognize values that match the hard-wired default
or environment variable value.)
regards, tom lane
tory in the user's profile.
In either case, the location can be overridden by setting ...
ISTR there's precedent elsewhere for doing it about like that.
regards, tom lane
hat the service file descriptions were worded
comparably.
regards, tom lane
(say) a run-time-variable
table name. You'd have to construct and execute a dynamic SQL string.
regards, tom lane
p Tablespace:
It looks to me like that will only appear for tables with non-default
tablespaces.
regards, tom lane
onnection.
regards, tom lane
elling you the originating
server version and pg_dump version.
regards, tom lane
to the domain doesn't create an explicit collation
requirement. (That is, the domain *doesn't* have a specific
collation attached to it, any more than type text does.)
regards, tom lane
ior as its
+underlying data type.
The underlying type must be collatable if COLLATE
is specified.
regards, tom lane
ails.
Maybe something else already updated the row since the cursor was opened?
That would change its CTID.
regards, tom lane
SELECT does. There is
*plenty* of time for another session to get in there if you've been
groveling through 50K records one at a time.
regards, tom lane
ind public.test10, so it's not accessible except by
qualification.
You can do "\dt *.*" or "\dt new.*", etc, to see such tables.
See here for more info:
https://www.postgresql.org/docs/current/app-psql.html#APP-PSQL-PATTERNS
regards, tom lane
;CODE:08006' or \
> $msg contains 'CODE:42501'\
> ) then ///xxx/pg_log/postgres_filter.log
You should realize of course that syslog is not a 100% reliable logging
mechanism -- at least most implementations are capable of dropping
messages under load. But we needn't guess about reasons for missed
messages here.
regards, tom lane
. You need to revoke that before other grants/revokes will
have any functional effect.
regards, tom lane
#x27;m vaguely aware that some packager
(Debian I think) has added an overlay of that sort; but you'd need
to consult the package-level documentation not the community docs
in order to find out more.
regards, tom lane
relying on CTID
is likely to be problematic.
regards, tom lane
ry via the --host option?
Usually you'd use -p (--port). You *could* specify the exact path
to the postmaster's socket via -h, but I think that's not idiomatic.
regards, tom lane
ow version.
regards, tom lane
t detuning your
setup for other queries.
You should probably also rethink whether you really want to store
your data in this format, because anything at all that you do with
that big JSONB column is going to be expensive. (Another thing
that's been on the to-do list for awhile is enabling partial
retrieval of large JSONB values, but AFAIK that hasn't happened
yet either.)
regards, tom lane
-> operator certainly doesn't.
regards, tom lane
er to join in exactly the syntactic join order.
regards, tom lane
structure. Sure, you can store tons
of unorganized data in a jsonb column, but you pay for that convenience
with slow access. Normalizing the bits you need frequently into a more
traditional relational schema is the route to better-performing queries.
regards, tom lane
people.
In a quick experiment here, I don't see any bison complaints if I
back it down to unreserved_keyword, so this seems easily fixable.
I wonder though if we don't need more review of patches that add
partially- or fully-reserved keywords.
regards, tom lane
ibed to that?
regards, tom lane
l, would the partial distribution
> not be safe to use ?
The hard part is to avoid double-counting the selectivity of the "is not
null" clause if you do that. It's something that would be nice to do
but it's much trickier than it sounds.
regards, tom lane
ld just
not build uuid-ossp; it's fairly vestigial these days, now that we
offer gen_random_uuid() in core.
regards, tom lane
d handle this as
EXEC SQL SELECT currtid2(:table ::text, :oldCTID ::tid) INTO :newCTID;
If you want full-on dynamic SQL, that's also possible but you'd need
PREPARE/EXECUTE, and it wouldn't look much like this fragment.
I don't see a need for that here, though.
regards, tom lane
ed.
As best I can tell, the issue Tim's unhappy about is not so
much the use of a nestloop as the lack of use of any index.
But "string like '%foo%'" is not at all optimizable with a
btree index. You might be able to get somewhere with a
pg_trgm GIN or GIST index.
regards, tom lane
th" indicates a null
field value.
regards, tom lane
a purist semantic point of view,
but having the operator throw an error in such cases would make it
close to unusable on not-uniformly-structured data. And really the
point of using JSON inside a SQL database is to cope with irregularly-
structured data, so fuzziness seems like what we want.
regards, tom lane
ion within GROUP BY groups, not windowing.
regards, tom lane
7;m also suspicious of the "// trim" code, which will misbehave
for a zero-length token.
regards, tom lane
exception", any more than you could trap other syntax errors
detected by the parser. (As an extreme example, you could certainly
not trap it if you misspelled "exception".)
regards, tom lane
te OID values within any one catalog
or TOAST table, and it doesn't particularly matter if there are
duplicates across tables.
regards, tom lane
ue, in case that's what the input is.
PG_GETARG_TEXT_PP is preferred in new code since it can avoid one
step of palloc-and-copy-the-value; the only real downside is you
have to use the appropriate macros to get the string's start address
and length.
regards, tom lane
Markur Sens writes:
> On 12 Jun 2022, at 12:06 AM, Tom Lane wrote:
>> PG_GETARG_TEXT_PP is preferred in new code since it can avoid one
>> step of palloc-and-copy-the-value; the only real downside is you
>> have to use the appropriate macros to get the string's start ad
o write a "validate_conversion" function that supports extension
datatypes, but doesn't use something morally equivalent to a
subtransaction, would be a nightmare: large, fragile, and probably
not all that much faster.
regards, tom lane
acle does something
like that already, or perhaps they're just ignoring the semantics
problem; they do not have a reputation for hewing closely to the
spec on behavior regarding nulls.
regards, tom lane
Daniel Brinzila writes:
> I am a bit confused as to the following change:
>Stop using query-provided column aliases for the columns of whole-row
>variables that refer to plain tables (Tom Lane)
> Could someone please give an example of this scenario, one that works in
> 11
"David G. Johnston" writes:
> On Tue, May 24, 2022 at 7:42 AM Tom Lane wrote:
>> Perhaps we could improve matters like this?
>> -specified, the underlying data type's default collation is used.
>> +specified, the domain ha
e SRPM for whichever version you want and seeing
if it doesn't build on your machine. Building from SRPMs is not hard,
and it's a good skill to acquire if you're using non-mainstream
hardware.
regards, tom lane
"David G. Johnston" writes:
> The fact that a domain over an array isn’t being seen as an array here
> seems like a bug.
Hmm. The attached quick-hack patch seems to make this better, but
I'm not sure whether there are any cases it makes worse.
re
it's effectively [4,10)?
What pitfalls does that create for, say, multirange operators?
You could usefully make a domain over the range type and put some
restrictions at that level, perhaps.
regards, tom lane
types as soon as
the CASE arms are discovered to not be all of the same type.
regards, tom lane
of connection timeout somewhere in
the git.postgresql.org infrastructure, causing a "git clone"
that takes more than a couple of minutes to fail. I've
complained about it before, but we've not isolated the cause.
regards, tom lane
, it's hard to guess at why it isn't;
maybe there's a data type issue?
>> Is Postgres unable to optimize the query similar to Oracle? Is it possible
>> this is possible but we are running on too old of a version?
> PostgreSQL 10 is quite old, so that's a possibility.
That's worked for many ages.
regards, tom lane
think we conservatively assume that any difference in
spelling is significant).
Best bet might be to edit the dump file to adjust the locale
spellings to match your new system.
regards, tom lane
d it handles all these variants.
So this doesn't seem like it should take much new code, though
maybe some refactoring would be needed to make the lookup code
available where this check is happening.
I'm not personally very excited about this, but if someone wanted
to prepare a patch...
backend/libpq/auth.c at least,
backend/libpq is unrelated to interfaces/libpq. (I've seen hints
that they arose from a common code base, but if so, that was a
few decades and a lot of rewrites ago.)
regards, tom lane
ecific practical case can't be proven.
Still, that result has discouraged most people from spending much
time on mechanically checking such things. If you declare a function
immutable, Postgres will believe you; the consequences if you lied
are on your own head.
regards, tom lane
[1] https://en.wikipedia.org/wiki/Halting_problem
Pavel Stehule writes:
> st 29. 6. 2022 v 7:46 odesílatel Tom Lane napsal:
>> ... that result has discouraged most people from spending much
>> time on mechanically checking such things. If you declare a function
>> immutable, Postgres will believe you; the consequences
_PROTOCOL(1234,5680)
So some client is running code new enough to try GSS protocol,
but the 9.6 server doesn't know what that is. You'd need v12
or later server if you don't want to see these complaints.
(But you could just ignore them.)
regards, tom lane
rom checkable.
There's more to it than that, but if there's not any attention
to crash recovery then it's not what I'd call a database. The
filesystem alone won't promise much here.
regards, tom lane
ite into pg_catalog. They can. But I don't see
much point in being paranoid about whether the contents of pg_catalog
are trustworthy. If an adversary has already obtained superuser
privileges, he needn't bother with anything as complicated as
trojan-horsing something you might call later.
regards, tom lane
all its schemas.
> Which implies REVOKE'ing grants on all those "db specific" ROLEs first.
You should not really have to revoke those manually.
The normal process for that is to use DROP OWNED BY.
https://www.postgresql.org/docs/current/role-removal.html
regards, tom lane
s), and that EDB's fork follows Oracle's datatype naming.
So I'd not be at all surprised by this result if it's on EDB.
BTW, Oracle doesn't really accept "::" casting notation does it?
I always thought that was a pure Postgres-ism.
regards, tom lane
starting psql with the '-n' switch.
Another fairly likely possibility is that your paste contains
invisible characters that psql does not think are whitespace,
like non-break space ( ). However, pasting into a file
wouldn't make that problem go away, so the tab idea seems
a shade more likely.
regards, tom lane
you're expecting a serial ID column to not
have holes in the sequence of values, you're going to be sadly
disappointed, whether you use ON CONFLICT UPDATE or not.
regards, tom lane
eleted)
...
And here we have the culprit, evidently ... but what the dickens
is it? I can't think of any mechanism within Postgres that would
create such an allocation.
regards, tom lane
s to know that.
At this point I suspect that PG 14.3 vs 14.4 is a red herring,
and what you should be looking into is what else you updated
at about the same time, particularly in the line of container
management tools or the like (if you use any).
regards, tom lane
#x27;t know.
regards, tom lane
the infinity to
> numeric it will fail. If that doesn’t happen the query won’t fail.
FWIW, PG 14 and later do support infinity in the numeric type.
regards, tom lane
es (e.g. update a one-row table). The point of sequence objects
is exactly to provide a feature with better concurrent performance,
at the cost of no rollback guarantees.
So, there's no bug here, and calling it one isn't going to change
anybody's mind about that.
regards, tom lane
good way
to deal with the inter-extension connection other than to give btree_gist
a hard dependency on citext, which people wouldn't appreciate too much.)
You could fake it with
exclude using gist (lower(foo) with =, bar with &&)
which is surely conceptually ugly, but I think it gives compatible
semantics.
regards, tom lane
lying some code details).
It's entirely possible that there isn't any solution other than fixing
your app to be more consistent about how it binds the parameter.
regards, tom lane
nlining would result in exposing the actual result
* of the function's last SELECT, which should not happen in that case.
So try adding STABLE to the function definition.
(This could be better documented, perhaps.)
regards, tom lane
's schema name if
we want the transform name to be unique.
Not sure whether it's worth venturing into such nonlocal fixes.
regards, tom lane
diff --git a/src/bin/pg_dump/pg_dump_sort.c b/src/bin/pg_dump/pg_dump_sort.c
index 5de3241eb4..2282c002ae 10064
bug fixes, and it's not improbable that the underlying issue
here is included in that.
If that doesn't help, you'll need to start debugging. The
symptom looks a bit like catalog corruption; if you are lucky
then REINDEX'ing the catalogs used in that query would help.
regards, tom lane
couple of grounds but it undoubtedly
leads to surprising results if you expect error conditions to be
recognized left-to-right or anything like that.
Of course, SQL commands themselves have to be analyzed in not
particularly left-to-right order, and we don't get that many
complaints about that.
regards, tom lane
t
code is running in some kind of sandbox that disallows IP
connections by default.
Also, does psql work when you say "psql -h localhost"? It's
possible that your server isn't listening on localhost, or
there's a firewall there. Your working connections could all be
via Unix sockets, from what little you've said so far.
regards, tom lane
INER; although that
makes the function's permissions those of the function's owner not the
view's owner.
regards, tom lane
I'd try that in a scratch installation
first ...)
There was some discussion not long ago about relaxing the check
for "same collation name" [1], but no one has written a patch.
regards, tom lane
[1]
https://www.postgresql.org/message-id/flat/fedc0205-c15b-e400-aa3f-e1d2a1285ddb%40sourcepole.ch
ent).
So that right there is two cases where we omit data for a column.
I suspect the "unchanged toasted data" case is what matters for
your purposes. Maybe you've found some code that fails to implement
that correctly?
regards, tom lane
.
Ah. I bet this is another instance of the known memory leakage problems
with JIT inlining [1]. Per Andres' comments in that thread, it seems
hard to solve properly. For now all I can recommend is to disable that.
regards, tom lane
[1]
https://www.postgresql.org/message-id/flat/20201001021609.GC8476%40telsasoft.com
rees not just the base Vars.
regards, tom lane
x27;d be interested.
regards, tom lane
1101 - 1200 of 2962 matches
Mail list logo
