ems to think it's a problem with aborting a DROP DATABASE.
Adding more data might serve to make the window wider, perhaps.
regards, tom lane
on of yylval; don't add one yourself.
BTW, this isn't right:
#define YYSTPYE string
first because you misspelled YYSTYPE, and second because you
evidently want yylval to be double not a string.
regards, tom lane
it to happen. People have already done that. (Searching
the mailing list archives might be edifying.)
regards, tom lane
appears in the headers of every mail sent
out by the postgresql mail list servers. That link is unique to your
address, so you won't need any username or password to make the
request take effect.
regards, tom lane
mply cannot expect
that code that looks at system catalogs is never going to need
to be touched when doing a major version upgrade.
regards, tom lane
e the TOAST pointer not the
detoasted value that would be passed through joins, sorts, hashes, etc.
And we really only care about how much space would be needed for
things like sort temp files.
regards, tom lane
e JSON operator table didn't link to it before v13.
(I agree that the "top level" bit was just wrong, but it's gone.)
regards, tom lane
Adrian Klaver writes:
> On 5/18/23 08:46, Tom Lane wrote:
>> You seem to be reading some fairly old version of the documentation.
>> The extended definition that Adrian mentions has been there for
>> awhile, but the JSON operator table didn't link to it before v13.
>&
issed out
support for that type. But the only core-PG suspect is
pg_stat_statements, and I can see that it does know that node type.
regards, tom lane
ith key-per-database is what are you going to do
with the shared catalogs? It's a lot simpler, and probably better
performing, to use one key per cluster.
regards, tom lane
you need to take it up with whoever provides "azure".
regards, tom lane
could use
rethinking, not sure.
regards, tom lane
ition (or ANDed conditions), you're in for
a world of hurt.
regards, tom lane
3 4 5}'::int2vector[];
int2vector
-
{"1 2","3 4 5"}
(1 row)
regards, tom lane
w. When I do
this I see
...
19
20
21
--More--
Since you're not getting a prompt but just the subsequent
\timing output, it seems that the rest of the output went
into the bit bucket, which psql would certainly never do
on its own. But a malfunctioning pager might act that way.
regards, tom lane
the INSERT, so we can resolve
the NULL as being of type int. But use of DISTINCT requires
resolving the type of the value (else how do you know what's
distinct from what?) and by default we'll resolve to text,
and then that doesn't match what the INSERT needs.
regards, tom lane
t have to drill down to the point of counting how
many files in the database's directory, if the individual indexes aren't
showing up as committed catalog entries yet.
regards, tom lane
looks like you already have such an
index, ie a GIN index on the desc_tsv column, although I don't trust
that your schema attachment is actually accurate because if it is
then you have a bunch of duplicative indexes. You might try
dropping the other indexes to see if you can coerce the planner
into using that one, and then seeing what the cost estimate is.
regards, tom lane
itions of the routes table, which will not be good for performance.
regards, tom lane
or many possible input characters,
notably spaces. I seem to recall that the default action in
such cases is to print the character on stdout.
The grammar lacks any way to deal with any input after the
first newline. Anything except EOF will draw a syntax error.
regards, tom lane
ply DISTINCT or some other non-trivial processing
in the upper query.
regards, tom lane
;" is not. It's not impossible in principle for "<>" to be an
index operator, but the set of cases where indexing on such a condition
would beat a seqscan is likely to be uselessly small. By the same
token, EXCLUDE constraints using such a condition would be unpleasantly
inefficient.
regards, tom lane
n is that "."
*does* match "'", so it's ambiguous what will happen with quotes.
You probably need something closer to [']([^']|\n)[']
regards, tom lane
ons, because that state is only backend-local.
regards, tom lane
like it'd take an enormous amount of new C code
that would then have to be kept in sync (by hand) with the backend
parser. Testing such a thing seems like a big time sink as well.
I seriously doubt that we'd be willing to take on such a maintenance
burden.
regards, tom lane
;?
Probably because a tty input device is not seekable.
regards, tom lane
product row.
We can do better than that if the OR'd conditions are each amenable
to an index scan on one of the tables: then it can be a nestloop with
a bitmap-OR'd inner index scan. I thought the upthread advice to
convert the substr() condition into something that could be indexed
was on
041008v50104fd8p6181d5ddce85a6a%40mail.gmail.com
but it doesn't seem to have gone anywhere.
regards, tom lane
A larger result set should show less percentage error.
regards, tom lane
re testing
> with very small result sets (say a couple hundred KB)
Sigh, obviously I meant a couple hundred *bytes* there. -ENOCAFFEINE
regards, tom lane
, it's a literal of unknown type,
with the actual type to be inferred from context. There is a small
preference for resolving such a thing as being of text type, but only a
small one. The rules are exactly the same as for an undecorated NULL
constant.
regards, tom lane
jian he writes:
> should I expect
> select pg_input_is_valid($$[now(), infinity)$$,'tstzrange');
> returns true?
No. "now()" is not a literal, it's a function call.
regards, tom lane
an existing temp schema in
the slot assigned to the current backend.
regards, tom lane
, volatility markings are a promise
by the user to the system, not vice versa. If you break your promise,
you get to keep both pieces of whatever trouble ensues.
regards, tom lane
and prior
versions. Observe also the v15 release notes:
https://www.postgresql.org/docs/15/release-15.html
E.4.3.4. Data Types
Allow the scale of a numeric value to be negative, or greater than
its precision (Dean Rasheed, Tom Lane)
This allows rounding of values to the l
all
those tables in one transaction.
regards, tom lane
[1] https://www.postgresql.org/message-id/3612876.1689443232%40sss.pgh.pa.us
fix for this error report in the upcoming v16, but psql commands
that involve local filesystem access will still not act very nicely if
psql can't read your directory.
regards, tom lane
me other database
to connect to, with no certainty of success; and (b) even if
it manages to connect to the server, there's no certainty
that you'd have permissions to create a new database.
So I don't believe any JDBC driver would even try.
regards, tom lane
t, a binary representation probably wouldn't be terribly
useful, as it'd contain role OIDs that wouldn't reliably transport
from one system to the next, and also privilege bitmasks that
we sometimes redefine.
regards, tom lane
ngs your main session is using. So what remains
to be explained is why you aren't seeing the same complaint when
starting a fresh session. It might be useful to look at the
output of
show default_text_search_config;
and
select * from pg_file_settings where name = 'default_text_search_config';
regards, tom lane
t should always exist?)
"public.pg" is certainly not a standard (as in built-in) text search
configuration name. Maybe that value was installed by some bit of
software that failed to install the configuration to go with it,
or only put the configuration into one database not everywhere in
your installation?
regards, tom lane
ma (for security reasons). You might see if a newer drupal release
is available. If not, the best bet would likely be
GRANT ALL ON SCHEMA public TO public;
If you run into more problems, a more drastic answer might be to
downgrade to whatever drupal considers a supported release of
Postgres.
regards, tom lane
t's not worth maintaining a separate libpq-only
build path.
regards, tom lane
e suggests that
you want to add
"--with-pgport" => 5433
(with the quotes, probably).
regards, tom lane
achine.
BTW, you can ignore the "could not change directory" warning.
That's expected when starting "sudo -u postgres psql" in a
directory that the postgres user can't read.
regards, tom lane
Aramaki Zyake writes:
> What should I do to move built artifacts into /usr/local/pgsql?
"make install", or possibly "sudo make install" if you'd rather
the installed files be root-owned.
https://www.postgresql.org/docs/current/install-short.html
regards, tom lane
regards, tom lane
sting on bug-compatibility with non-SQL-compliant details
of some other DBMS, and you can't adjust the application at all,
there is going to be some new showstopper problem biting you
every day.
regards, tom lane
[1] https://www.postgresql.org/docs/current/catalog-pg-cast.html
The text search functionality is already case-insensitive, but not
accent-insensitive (at least in the common built-in configurations).
To make it accent-insensitive, you can set up a custom configuration
using the "unaccent" module. See
https://www.postgresql.org/docs/current/unaccent.h
the JDBC driver
has its own notion of custom vs generic execution, so maybe the
issue is around there somewhere.
regards, tom lane
in-support oracle_fdw version.
regards, tom lane
[1] https://www.postgresql.org/support/versioning/
Please speak to Greenplum customer
support, rather than expecting the wider Postgres community to help
you for free with a code base that we don't even know.
regards, tom lane
he access to readonly to make sure it has the read
> access to NEW tables created by readwrite user?
The readwrite user (not the admin) would need to issue ALTER DEFAULT
PRIVILEGES granting that.
regards, tom lane
happening, to see what may be waiting on what?
regards, tom lane
dy else's lock. But you need to look to see which session is
holding a lock on mvw_cbsd_status_grants_lessinfo_active_softmarker
and what it's doing.
regards, tom lane
leges, which is then modified per whatever command you
are giving. After that the privileges will always be explicit.
There's been occasional discussion of changing this behavior, but
it'd take work and it'd likely add about as much surprise as it
removes. People have been used to this quirk for a long time.
regards, tom lane
ll" for this might be a reasonable
thing to do too. I'm actually a bit surprised that that doesn't
work already.
regards, tom lane
ch path assumptions. postgres_fdw runs remote queries
with a very minimal search_path setting, so that unqualified references
to non-built-in objects are likely to fail.
regards, tom lane
Erik Wienhold writes:
> Anyway, I prepared a patch for the docs.
I think the last hunk of this is plenty sufficient, and the earlier
ones just add noise.
regards, tom lane
blocks, functions,
or procedures. If you're going to execute the same code over and
over within a session, a function or procedure will probably be
a better choice than re-issuing identical DO blocks.
regards, tom lane
ying that SAVEPOINT is unsupported.
ROLLBACK in plpgsql is a different command with different syntax
options than the core grammar has. So this is a matter of when
syntax errors are detected vs. when semantic errors are detected.
regards, tom lane
ke your own, or try to persuade
the glibc maintainers that they are wrong.
regards, tom lane
ovide a self-contained example. The people who might be
able to fix this are too busy to guess about what you are seeing.
regards, tom lane
either. Is that the *exact*
spelling of the message? Are you sure it's not coming from your
client-side code?
regards, tom lane
Erik Wienhold writes:
> On 07/09/2023 21:09 CEST Tom Lane wrote:
>> There is no such string anywhere in the Postgres source code;
>> furthermore, if someone tried to add such an error, it'd get rejected
>> (I hope) as not conforming to our style guidelines. I thought
gzh writes:
> In the Release Notes for PostgreSQL 12.14, we saw the following change:
> https://www.postgresql.org/docs/release/12.14/
>> Add recursion and looping defenses in subquery pullup (Tom Lane)
>> A contrived query can result in deep recursion and unreasonable amounts
ing
that you really need to see the results of.
I'm not sure whether it'd be profitable to try to build that behavior
into the scripts themselves. One problem is that "/dev/null" doesn't
have that name on Windows, so it's hard to see how to invoke the behavior
in a platform-agnostic fashion.
regards, tom lane
object file: No such file or directory
> no data was returned by command ""/mga8/usr/bin/postgres" -V"
You might get useful info from "ldd /mga8/usr/bin/postgres"
about where that executable is looking for libssl.
regards, tom lane
only shows it looking in /lib64, maybe you need a symlink there?
Alternatively, try ldd on the libssl.so.1.1 file itself, to see if it
has unresolved dependencies. I'm not totally sure, but I think indirect
unresolved dependencies might display this way.
regards, tom lane
roblem that we've created a
way for COMMIT PREPARED to fail, which ideally it should never do.
So I think there are indeed semantic issues, it's not entirely
a matter of "nobody got around to it".
regards, tom lane
s
that that connection wasn't ssl-encrypted).
You could adjust your connection parameters on the client side to
prevent the useless non-SSL connection attempt. But of course the
real question is how come the password authentication failed in
the first attempt. Looking into the server's log might yield
a clue.
regards, tom lane
oding in the pg_enc enum has seemed like a mostly
hypothetical problem because of that restriction.
regards, tom lane
ocess's environment
variables can readily be inspected by other processes. You should
check your platform carefully before assuming that PGPASSWORD is
a safe way to pass down a secret.
regards, tom lane
t care to open.
regards, tom lane
Ron writes:
> Is there a way to define the SETOF record on the fly, like you do with
> RETURNS TABLE (f1 type1, f2 type2)?
Doesn't RETURNS TABLE meet the need already?
regards, tom lane
Ron writes:
> On 9/26/23 12:46, Tom Lane wrote:
>> Ron writes:
>>> Is there a way to define the SETOF record on the fly, like you do with
>>> RETURNS TABLE (f1 type1, f2 type2)?
>> Doesn't RETURNS TABLE meet the need already?
> That rationale means th
Alexander Petrossian writes:
> 25 сент. 2023 г., в 17:28, Tom Lane написал(а):
>> you’d have a big problem with being able to change the behavior of
>> security-definer functions.
> Could you please elaborate on this, Tom?
pldebugger allows you to change the contents of
#x27;t know how to do a lot of operations on it.
Type "point" and related animals are sort of a poor man's array,
which is supported for basic subscripting operations, but it's not
generic enough to be reasonable to consider as an ANYARRAY.
regards, tom lane
to ENCODING 'ISO-8859-1' makes me wonder what
encoding conversion is being performed.
regards, tom lane
n.
It's hard to get much further than that with the info that
we have.
regards, tom lane
cal contents, I think there's
a DB comparison tool that's been recommended around here.)
regards, tom lane
omation for the existing conversion processes involving table
rewrites. That's possible perhaps, but it doesn't really sound
compelling enough to justify a lot of work.
regards, tom lane
ed
to find another way to transcode the data that was in that encoding.
Probably, running your database in UTF8 is the best choice -- we
can convert most anything to that.
regards, tom lane
n do to make their row locking orders be reliably
consistent. Or see if you can avoid needing exclusive row
locks in the first place.
regards, tom lane
ng as I put quotes around the URL.)
regards, tom lane
why the docs are silent on the point.
regards, tom lane
triggers
restoring the previous zone when the function exits; simpler
and probably faster than coding the save/restore explicitly.
Side note: whether this is really "immutable" is a matter for
debate, since time zone definitions tend to change over time.
But we chose to mark the new 4-argument version that way,
so you might as well do so too.
regards, tom lane
d an ORDER BY for the overall query
result, the implementation is entitled to return the rows in
any order it pleases. Ours happens to sort by the window ordering
before computing the window functions, so that's what you get.
In this case anyway --- you shouldn't rely on that.
setting seems less confusing.
> Does that mean I could run this
> outside this context of a function, and expect the setting to go back to
> UTC on a rollback?
An actual rollback would undo the effects of set_config, yes. You
only need this function wrapper to ensure that subsequent operations
in the same transaction don't see the setting change.
regards, tom lane
keep in mind is that that might have different
behavior in terms of the evaluation of the arguments to the function,
ie which timezone setting is your input parsed according to.
regards, tom lane
his doesn't affect you. What I was thinking
about was that
select generate_series('2023-10-04 13:30', ...)
is going to mean different things depending on the zone setting
that prevails when that constant is parsed.
regards, tom lane
is, but it was at least
thought about. I do agree with it as far as the default column
list goes, but maybe we could allow explicit selection of these
columns in COPY TO.
regards, tom lane
don't really see any backwards-compatibility problem with
allowing cases that had been errors, though.
regards, tom lane
ke the extra log entries, there's a command-line
switch that forces psql to prompt for password before connecting
the first time. Of course, that might result in prompting for
a password that's not really needed.
regards, tom lane
his is difficult to do without breaking
mountains of backend code, but there's been some discussions about
ways to accomplish that. The most recent thread I could find is
https://www.postgresql.org/message-id/flat/CALSd-crdmj9PGdvdioU%3Da5W7P%3DTgNmEB2QP9wiF6DTUbBuMXrQ%40mail.gmail.com
regards, tom lane
duce, not increase, the set of strings we'll call identifiers.
regards, tom lane
r helpful info at
https://wiki.postgresql.org/wiki/Corruption
regards, tom lane
t follow its basic control flow. Indent
according to the brace structure, and your life will get easier.
regards, tom lane
eges for the user in all databases in the cluster using one view,
> select.
This is not possible, because a session can only see the catalogs for its
own database (plus the shared catalogs, but those only describe shared
objects).
regards, tom lane
slashes in
the default format. You could use CSV format, perhaps, but that
has its own quoting rules that also mean that what comes out is
not going to be json-and-nothing-but. See "File Formats" here:
https://www.postgresql.org/docs/current/sql-copy.html
regards, tom lane
1801 - 1900 of 2962 matches
Mail list logo
