bootstrap superuser might not be named postgres
(it'll be named after whichever OS user ran initdb). However, your "\du"
output pretty clearly shows you have no superuser, and that's just odd.
regards, tom lane
you need to
look at the kernel firewall (packet filter) settings.
regards, tom lane
search_path setting you're using from PHP.
regards, tom lane
ld do so.
It's a matter of finding people with the time, interest, and technical
ability.
regards, tom lane
pect compression opportunity losses to more or less balance out
with opportunity gains over such a large data volume, but maybe you
were unlucky. Or perhaps the move into a single table was done in
such a way that it actually decreased locality-of-reference, eg maybe
similar rows were grouped before and now they're not.
regards, tom lane
verything else copes.
I think we should probably sanitize custom GUC names at least to the
extent of forbidding '=' and '-'. Maybe we should go further and
insist they look like regular identifiers.
(Fortunately, ALTER USER SET with a custom GUC is superuser-only,
so there's no need to worry about security issues here. But we
should eliminate surprises.)
regards, tom lane
/usr/lib/libedit.3.dylib (compatibility version 2.0.0, current version
3.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 1292.60.1)
of which the relevant bit for this purpose is "/usr/lib/libedit.3.dylib",
pointing to the Apple-supplied version of libedit. Maybe you see
something else?
regards, tom lane
libreadline is fairly configurable, so maybe this boils down
to some unintentional change in your ~/.inputrc ?
regards, tom lane
butes]
Huh. What compiler are you using, exactly? Perhaps you used a different
compiler when running configure (or are trying to re-use configure results
from some other machine)?
regards, tom lane
igure output clearly shows that it thought gnu_printf
is fine:
checking for printf format archetype... gnu_printf
Possibly the corresponding section of config.log would provide more
insight.
regards, tom lane
tting built with "c++", so now I wonder
exactly which compiler that is.
You could probably suppress these complaints by passing "CXX=g++"
to configure. Or at least, you could if g++ was installed, but
I think configure will default to that if it can find it...
regards, tom lane
o the trick.
regards, tom lane
there
are optimization fences both above and below where the WHERE clause is.
You have one above from the LIMIT 1, but (with the new interpretation of
CTEs) not one below it. Adding a fence -- either OFFSET 0 or LIMIT ALL --
to the first CTE should fix it in a reasonably version-independent
fashi
ry if I saw server startup
failures. These values do *not* constrain what you can set for
shared_buffers or the like; at most, they'd constrain how many PG
instances you can run on one machine.
regards, tom lane
arly opposites.
Perhaps a different name should have been chosen, but we're
stuck now.
regards, tom lane
ps Oracle is more forgiving of such things than
PG is.
regards, tom lane
t to 0.
> Can anyone confirm (or refute) that the behavior I see on my Mac
> (preservation of these values through a restart) is common & expected
> behavior?
Yeah, in PG those stats would be preserved, at least as long as it's
a clean shutdown.
regards, tom lane
at
for it. While that's annoying, it's also good practice. Functions
that could be invoked in these contexts really ought not assume
what search path they are called with.
I do not think any of the other details you mentioned, such as
use of --role, have any impact on this.
regards, tom lane
Ken Tanzer writes:
> On Thu, Feb 18, 2021 at 8:44 PM Tom Lane wrote:
>> There was a security change to pg_dump a few years ago to make it
>> put "set search_path = pg_catalog" into the dump script. This
>> basically means that any user-defined function in indexe
public schema is
world-writable, though, you're in big trouble anyway ...
regards, tom lane
..', the backslashes are eaten by the string literal
parser. So the pattern seen by regexp_replace() is just '(.*)', in
which the parens are capturing parens not literal characters. Thus it
matches the whole string.
Personally I'd leave off the E, but if you must use it then double the
backslashes.
regards, tom lane
resql.org/wiki/Locale_data_changes
you should be okay for rhel/centos 6 to 7 migration unless you
use de_DE locale. But I don't know how thorughly that's been
checked.
Using logical not physical replication might be safer.
regards, tom lane
s department, but I don't
think that's very portable. Moreover, even on Linux there's no
way to detect whether any of the writes failed.
Barring some solution to those problems, we would be unlikely to take
a patch that uses sync() instead of fsync().
regards, tom lane
m type. As of v13 I don't think there's anything in
that area that custom types can't replicate ... but there certainly
is plenty of infrastructure for the standard types that you'll need
to build out if you want equivalent functionality.
regards, tom lane
s://www.postgresql.org/docs/13/gin-extensibility.html
After reading that, I'd suggest looking into the code for gin opclass
support in various contrib modules (hstore might be a good start).
regards, tom lane
hose functions work
The support functions need to know about the operators' semantics, so
you have to write your own when inventing new operators.
regards, tom lane
Ayo writes:
> On 2021-02-23, Tom Lane wrote:
>> The slow query isn't using the chars_pkey1 index, which makes one
>> wonder if you have a corresponding index in the custom-type case,
> The index exists and is usable in the custom-type case:
Hmm. The next most li
Santosh Udupi writes:
> Right. pg_dump under the pgAdmin runtime folder works perfectly. pg_dump
> in postgres13 (ubuntu) does not work. Exact same syntax.
So, are these identical pg_dump versions? We did fix some things
in this area in 13.2.
regards, tom lane
erator class?
Hmm ... did you remember to set the oprcanhash property on the equality
operator?
regards, tom lane
e hash or btree
(respectively) opclass.
regards, tom lane
Hmm ... well, that would be a regression, but you're going to have
to show us how to reproduce it. I'm thinking there must be something
odd about the way the table is declared.
regards, tom lane
Yambu writes:
> Is there a reason why i'm getting text when i run the below
> select convert_to('some_text', 'UTF8')i get back 'some_text'
You must have bytea_output set to "escape".
regards, tom lane
ly because it doesn't handle cases like null entries.
If you're in need of that, my suggestion is to ditch intarray.
regards, tom lane
#x27;t understand is the [,...] part, i.e. optionally repeating
> argument.
You can repeat the host[:port] part, no more.
regards, tom lane
? Seems like that would clarify how much you can repeat.
regards, tom lane
=?utf-8?Q?Paul_F=C3=B6rster?= writes:
>> On 25. Feb, 2021, at 16:22, Tom Lane wrote:
>> Hmm. Maybe
>> postgresql://[user[:password]@][host[:port][,...]][/dbname][?param1=value1&...]
>> ? Seems like that would clarify how much you can repeat.
> yes, that looks
n integer array
using the built-in array opclass. It might be a shade slower than
intarray, but maybe it's 120ms instead of 100, and it'll handle
nulls correctly.
regards, tom lane
of course not the advice to use COPY.
regards, tom lane
tantially different in meaning from the main copyright
notice. This is also true of bits of the core server, actually.)
Extensions you get from elsewhere might have different copyrights though.
regards, tom lane
ostspec is [host][:port][,...]
Also, the paramspec is under-bracketed today. Should be
more like
paramspec is param=value[&...]
regards, tom lane
that it
>> refers to either of both host *and* port.
> I think an easier fix is to move the repeat to the main line, i.e., make
> it "hostspec[,...]" and then hostspec is only [host][:port].
WFM. Who's going to write the patch? (I can, but if one of you
wants to, be my guest.)
regards, tom lane
t those are needed to clarify what
you can repeat; I think they add confusion not clarity. Besides,
the adjacent text and examples make this quite clear.
regards, tom lane
ot; since
your last successful PG build? Do you have either MacPorts or Homebrew
stuff on this machine?
FWIW, I don't think we've changed anything in this immediate area in
quite some time. So I guess something in your environment changed,
but it's not clear what.
regards, tom lane
stem catalogs seems like a really
bad one. Why not pass the code through sed or the like ahead of
feeding it to psql? But you'd have to get the regex syntax right
in any case.)
regards, tom lane
re schemas for temporary tables, which you cannot VACUUM outside the
> session that created them, so you can safely ignore these errors.
Indeed, but I'm wondering why vacuumdb isn't skipping them
automatically. Something fishy seems to be happening there.
regards, tom lane
ing anywhere near a temp table.
regards, tom lane
there. I think you can just do
\dt pg_temp_*.*
in psql (as superuser) to see what's out there. Figuring out which ones
are live sessions' temp tables might be harder, though.
regards, tom lane
Suresh Kumar R writes:
> When I query that table I need the pg_typeof(column) as record[] instead of
> composite_type[].
Why? record[] is considered a pseudotype (polymorphic type),
which is why casting to it doesn't do anything.
regards, tom lane
at our FTS features have basically been on autopilot
since they went in. I'd sort of hoped that we'd see more
parsers, more ranking functions, etc, over time ... but nothing
like that has happened. I'm not sure if that's just lack of
interest, or if people find the code too difficult to work with.
regards, tom lane
ther ranking function.
The documentation is pretty clear that they don't, they just consider each
document in isolation. Building a structure that would allow more-global
info to be taken into account is an interesting project that nobody's
tackled.
regards, tom lane
source-filesystem-13.0.0-3.fc35.aarch64
gcc-11.2.1-9.fc35.aarch64
gcc-c++-11.2.1-9.fc35.aarch64
llvm-13.0.0-4.fc35.aarch64
llvm-devel-13.0.0-4.fc35.aarch64
llvm-libs-13.0.0-4.fc35.aarch64
llvm-static-13.0.0-4.fc35.aarch64
llvm-test-13.0.0-4.fc35.aarch64
Don't think I can readily install anything as old as LLVM 9 ...
regards, tom lane
hubert depesz lubaczewski writes:
> On Fri, Mar 04, 2022 at 02:09:52PM -0500, Tom Lane wrote:
>> I tried and failed to reproduce this on Fedora 35 on aarch64,
>> but that has what I think is a newer LLVM version:
> I have suspicion that it also kinda depends on number of rows
Mladen Gogala writes:
> On 3/4/22 17:03, Tom Lane wrote:
>> Mmm ... it might have just been that the planner chose not to use
>> JIT when it thought there were fewer rows involved. Did you check
>> with EXPLAIN that these cut-down cases still used JIT?
> This is int
ient-side stack wants a type OID for a result column,
it's unlikely to be satisfied with a pseudotype OID anyway.
That provides next-to-no useful information about how to
interpret values. Are you sure you can't just leave the type
unspecified (e.g. zero) in whatever API is giving you trou
hubert depesz lubaczewski writes:
> On Fri, Mar 04, 2022 at 05:03:14PM -0500, Tom Lane wrote:
>> Mmm ... it might have just been that the planner chose not to use
>> JIT when it thought there were fewer rows involved. Did you check
>> with EXPLAIN that these cut-down cases
ontact
--
(John,Doe)
(1 row)
A bit tedious to set up, but it would have some advantages, eg you
could provide default values.
regards, tom lane
t my raspberry pi 3B+
is sufficiently different hardware from your box as to not
see the problem. Doubt that though.)
Can you create a self-contained test case?
regards, tom lane
pection_id_fk" on table
> "inspection_weather"',))
> Is there a way to get the DETAIL part as well?
It's not very well documented AFAICS, but a SPIError object has a
"detail" attribute, so "e.detail" should help you. It looks like
you might prefer to print "e.spidata", which seems to contain all
the available fields.
regards, tom lane
rc/backend/storage/lmgr/README-SSI, which might or might
not be the level of detail you are looking for.
regards, tom lane
BLOCKSIZE and associated comments, starting about
line 90 in fe-exec.c. I don't recall whether there was any specific
motivation for PGRESULT_DATA_BLOCKSIZE to be 2K rather than some
other value; but it wouldn't do for it to be very small.
regards, tom lane
t quite sure why order should matter.
regards, tom lane
hen have the delete queue up waiting for the lock
> to be removed?
With the amount of detail you've provided (viz: none), it's impossible
for anyone to guess what your problem actually is, let alone speculate
on suitable solutions.
regards, tom lane
s a procedure not a function, you can explicitly COMMIT
what's been done so far, and then your next action starts a new
transaction. But without such measures, all actions executed by
a function are part of the same transaction as the calling statement.
regards, tom lane
always returns 0.
What PG version is this exactly? What is in $PGDATA/pg_notify/ ?
regards, tom lane
down request
2022-03-15 10:07:48.244 EDT [315456] LOG: database system is shut down
None of this gets us any closer to understanding where the signal
came from, unfortunately.
regards, tom lane
r later, where that
code has been improved.
regards, tom lane
.
If the index was on a string type (text/varchar), the most likely
explanation is a switch to a different OS version with inconsistent
collation rules. See
https://wiki.postgresql.org/wiki/Locale_data_changes
regards, tom lane
ake this work better than it did in older
versions; but I can't tell from the log messages whether the
issue being fixed was new-in-14 or not.)
regards, tom lane
perhaps the underlying
> problem is there?
This definitely looks like the problem is on the client side not the
server side. It might be worth asking on pgsql-jdbc to see if it's
that driver or not; but it could be coming from somewhere else in
the Java ecosystem.
regards, tom lane
tQUEL language. Dunno what the SQL standard has
to say on the subject --- but it wouldn't surprise me if they don't
allow it.
regards, tom lane
any case they're less stable across major versions than the SPI APIs.
So it's a tradeoff.
regards, tom lane
er is perfectly capable of ignoring those by itself,
though. (Awhile back I tried to remove that psql behavior,
but it caused too much churn in our regression tests.)
regards, tom lane
t, or changed how the server counts lines within
a query, we concluded that this would confuse too many people and
break too many applications; so we left it alone.
(As of v15, psql will send -- comments that begin *after* the
first non-whitespace token of a query [1]. But leading comments
and whi
We follow that spec, so depending on what
DIN 91379 *actually* says, we might have additional reasons not to be in
compliance. I don't read German unfortunately.
regards, tom lane
[1] http://www.faqs.org/rfcs/rfc3629.html
llback on any problem without causing an abnormal data state regarding
> the program.
Hmm, are you dropping and re-adding the reference-side indexes as part of
the same transaction that is doing this? I'm too short of caffeine to
recall details, but I think there are cases where a newly-made index
cannot be used right away.
regards, tom lane
immutable function applied to constant(s), the planner prefers
to fold to a constant by just executing the function. The inline-ing
transformation is considered only when that case doesn't apply.
regards, tom lane
is is the same problem already reported at [1].
It's an unfortunate error in the GIST ltree opclass.
You could apply the patch [2] locally perhaps, if you
don't want to wait around for 14.3.
regards, tom lane
[1]
https://www.postgresql.org/message-id/flat/17406-7
e table and
leaving a broken view behind isn't good. Neither is refusing to
let the owner drop her object.
regards, tom lane
database or table context like other
> autovacuum settings?
There's an autovacuum_freeze_min_age reloption, isn't that
what you need?
regards, tom lane
anefficient.com
This might be more on-point:
https://www.postgresql.org/message-id/flat/CAJcOf-cAdMVr7azeYR7nWKsNp7qhORzc84rV6d7m7knG5Hrtsw%40mail.gmail.com
regards, tom lane
in name order. Uniqueness
constraints are not enforced by triggers though; I wouldn't care
to rely on the order in which those are checked.
regards, tom lane
d surely
make the hint a confusing mess.
Another way to look at it is that there are only two allowed
semantic behaviors here: INNER and LEFT joins. The fact that
there's more than one way to spell an inner join is a historical
accident.
regards, tom lane
blic' got removed from grantee?
> I'm going to say someone read this:
> https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058:_Protect_Your_Search_Path
> And did something along the line of this:
> REVOKE CREATE ON SCHEMA public FROM PUBLIC;
Note that that only recommends removing CREATE, though, not USAGE
which is what Rob seems to be lacking.
regards, tom lane
export CPPFLAGS="-I/usr/local/opt/openssl@1.1/include"
would need to be applied while *building* Postgres. If you've
already built it, or are trying to install a prebuilt package,
those flag settings won't do anything.
regards, tom lane
dropped.
This addition might be worth making, though.
(likewise for the other instances, of course)
regards, tom lane
ing pg_type could be advisable.)
2. Check for bogus entries in pg_depend:
select * from pg_depend where objid = 75083631;
select * from pg_depend where refobjid = 75083631;
3. If there's just one hit in pg_depend then it's probably
safe to delete that row.
regards, tom lane
you're not supposed to use parameter names
in \df, only their types. It seems like whitespace ought
to be allowed though.
regards, tom lane
gument parsing in \df and \sf.
regards, tom lane
"David G. Johnston" writes:
> On Fri, Apr 15, 2022 at 2:20 PM Tom Lane wrote:
>> While I've not yet looked at the code, I've got no reason to think
>> this is anything except fragile argument parsing in \df and \sf.
> I'm unsure about the "
of v14, so maybe the details don't have a huge constituency yet.
regards, tom lane
ferencing
column. PG doesn't require one to exist to create an FK; but if you
don't, deletes of referenced rows had better be uninteresting to you
performance-wise, because each one will cause a seqscan.
regards, tom lane
Perry Smith writes:
> On Apr 16, 2022, at 10:33, Tom Lane wrote:
>> The most obvious question is do you have an index on the referencing
>> column. PG doesn't require one to exist to create an FK; but if you
>> don't, deletes of referenced rows had better be unin
rst. But there could be other version-skew
problems lurking behind this one, so prodding the formula maintainer
seems to be the easiest path.
regards, tom lane
Linux, what does "sysctl crypto.fips_enabled" say?
(This theory also requires that v14 was built with openssl support.)
FWIW, v15 will provide a more on-point error message in such cases.
regards, tom lane
"Pete O'Such" writes:
> Yup, FIPS-mode is on for both ends. I'd love a pointer to docs or other
> resources for figuring out what the path forward looks like.
You could switch to SCRAM passwords, if you don't need to support any
clients using pre-v10 libpq.
at. Manual vacuuming isn't going to help until you get rid
of the old open transaction. Look into pg_prepared_xacts and
pg_stat_activity.
regards, tom lane
emantic rule) but perfectly valid to write syntactically.
I'm not sure that that's actually disallowed. In any case, Bryn's
right, the combination of a SET clause and a PARALLEL clause is
implemented incorrectly in AlterFunction. Careless coding :-(
regards, tom lane
fore set_items fixes the problem, as in the
>> attached.
> This time with the file.
Yeah, I arrived at the same fix. Another possibility would be to
make the procForm pointer valid again after heap_modify_tuple,
but that seemed like it'd add more code for no really good reason.
regards, tom lane
I'm not sure that insisting that that stanza be
last is especially useful advice for future hackers, because someday
there might be more than one variable-length field that this function
needs to update.
regards, tom lane
ssion that is about to begin using
a temp schema will clean out any surviving contents.
So if you rewound to a point where some temp objects exist, it'd be the
responsibility of the first session that wants to use a given temp schema
to clean out those objects.
regards, tom lane
1001 - 1100 of 2962 matches
Mail list logo
