On Fri, Jul 15, 2022 at 12:40 PM Justin Pryzby wrote:
>
> That appears to be copied from the INSERT page.
> What does that mean, if not that data types will be resolved as needed ?
>
Yep, and the system needs to resolve the type at a point where there is no
contextual information and so it
On Fri, Jul 15, 2022 at 12:40 PM Justin Pryzby wrote:
> On Fri, Jul 15, 2022 at 12:17:51PM -0700, David G. Johnston wrote:
> > On Fri, Jul 15, 2022 at 11:40 AM Alvaro Herrera
> wrote:
> > > On 2022-Jul-15, Justin Pryzby wrote:
> > >
> > > > It seems a
On Thu, Jul 14, 2022 at 6:36 AM PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/12/functions-admin.html
> Description:
>
> Hello!
> There is no information in documentation about pg_advisory_unlock with
On Thu, Jul 14, 2022 at 3:57 PM Tom Lane wrote:
> Bruce Momjian writes:
> > On Mon, Apr 25, 2022 at 08:33:47AM -0700, David G. Johnston wrote:
> >> Both the location and name of the linked to section make no sense to me:
> >> https://www.postgresql.org/docs/c
On Fri, Jul 15, 2022 at 11:40 AM Alvaro Herrera
wrote:
> On 2022-Jul-15, Justin Pryzby wrote:
>
> > It seems a bit odd that it's impossible to use merge with prepared
> statements
> > without specifically casting the source types (which I did now to
> continue my
> > experiment).
>
> I have no
On Fri, Jul 15, 2022 at 6:27 AM Japin Li wrote:
>
> >
> > +servers. If setting max_wal_senders to
> > +0 consider also reducing the amount of WAL
> produced
> > +by changing wal_level to
> minimal.
> >
> > I don't think this is great advice. It will encourage people to
On Thu, Jul 14, 2022 at 6:08 PM Bruce Momjian wrote:
> On Wed, Feb 9, 2022 at 01:02:51PM +, PG Doc comments form wrote:
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/14/sql-createtableas.html
> > Description:
> >
> > If
On Thu, Jul 14, 2022 at 2:41 PM Bruce Momjian wrote:
> On Fri, Jul 8, 2022 at 10:55:55PM -0400, Bruce Momjian wrote:
> > > The/that inconsistency ... choose one. Or actually, the "an ... the"
> > > combination you used elsewhere doesn't grate on the ear either.
> > >
> > > + For each
On Thursday, July 14, 2022, Shay Rojansky wrote:
>
> If there's a guarantee that UNION ALL preserves ordering - as Tom seems to
> indicate in the thread quoted above - then the above works. If there's no
> such guarantee, then AFAIK the above can't be rewritten; putting the ORDER
> BY outside -
On Wed, Jul 13, 2022 at 10:02 PM Bryn Llewellyn wrote:
>
>
>
> * The owner name | The *identifier* for the owner
> name +- Joe
> | "Joe"*
>
> This is what I've been banging on about all the time. It seems that I'm
> the only person in the
On Wed, Jul 13, 2022 at 4:33 PM Bryn Llewellyn wrote:
>
>
>
>
>
> * role_name - Bllewell Exotic Me "Exotic Me" "Bllewell"*
>
> Of course I understand why I see both Exotic Me with no quotes and "Exotic
> Me" with double quotes: I asked for it. But why do I see both Bllewell with
>
On Wed, Jul 13, 2022 at 5:08 PM Shay Rojansky wrote:
> Greetings.
>
> I was trying to understand what - if any - are the guarantees with regards
> to ordering for combining queries (UNION/UNION ALL/...). From this
> message[1], it seems that UNION ALL does preserve the ordering of the
> operand
On Wed, Jul 13, 2022 at 7:58 AM André Hänsel wrote:
>
> SELECT last_value FROM t_id_seq;
>
>
>
> This will yield “8”, showing that new sequence numbers have been generated
> for each attempt.
>
Yep, an entire able-to-be-inserted tuple is formed every time. That
requires evaluating defaults so
On Wednesday, July 13, 2022, André Hänsel wrote:
> The wiki entry https://wiki.postgresql.org/wiki/UPSERT kind of suggests
> that with the introduction of ON CONFLICT DO UPDATE the problem of upserts
> is solved. But is it?
>
>
>
> A common use case for upserts is to keep a table up to date from
On Tuesday, July 12, 2022, PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/14/tutorial-createdb.html
> Description:
>
> Hello,
>
> I'm new to postgres so following through the steps in "Chapter 1. Getting
On Sat, Jul 9, 2022, 08:16 Bruce Momjian wrote:
> On Sat, Jul 9, 2022 at 08:06:21AM -0700, David G. Johnston wrote:
> > Maybe invoke the wording from the libpq docs and say:
> >
> > The default database name is the same as the user connection parameter.
> >
> >
On Friday, July 8, 2022, Bruce Momjian wrote:
> On Fri, Jul 8, 2022 at 10:17:11PM -0400, Tom Lane wrote:
> > Bruce Momjian writes:
> > > On Tue, Jul 5, 2022 at 08:20:25PM -0400, Tom Lane wrote:
> > >> I agree this phrasing needs some work, but "resolved" doesn't seem
> > >> helpful, since
On Friday, July 8, 2022, jian he wrote:
> Hi, there.
>
> Not sure this is a bug, or intentional.
> select '[1, )'::int8range; --fail.
> select '[1,)'::int8range; --ok.
>
> tested on pg14.4, pg15.1
>
>
It is documented so I’d say intentional.
“Whitespace is allowed before and after the
On Wed, Jul 6, 2022 at 1:47 PM Bryn Llewellyn wrote:
>
> It seems that the wording is wrong here:
>
> « The value for search_path must be a comma-separated list of schema
> names. »
>
> It's schema identifiers—and not schema names. Yes?
>
>
To add further clarity (or confusion) there is also
On Wed, Jul 6, 2022 at 1:13 PM Bryn Llewellyn wrote:
> *david.g.johns...@gmail.com wrote:*
>
> At the level of discussion you want to have when you encounter unfamiliar
> syntax please read the syntax chapter for the related concept (expression
> identifiers).
>
>
>
On Wed, Jul 6, 2022 at 11:50 AM Bryn Llewellyn wrote:
>
> It succeeded. And the \d metacommand showed me that I now have a table
> pg_temp_3.x. Using a different database, it ends up in "pg_temp_1. What's
> going on here? Is "pg_temp" a kind of generic nickname for ANY "pg_temp_N"?
>
> I hate to
On Wed, Jul 6, 2022 at 10:24 AM Matthias van de Meent <
boekewurm+postg...@gmail.com> wrote:
> On Thu, 9 Jun 2022 at 18:12, David G. Johnston
> wrote:
> >
> > Per suggestion over on -docs:
> >
> >
> https://www.postgresql.org/message-id/bl0pr06mb4978
On Wed, Jul 6, 2022 at 10:03 AM Christophe Pettus wrote:
>
>
> > On Jul 6, 2022, at 09:48, Bryn Llewellyn wrote:
> > Neither causes an error. The "show", in each case, prints the bare value
> with no quotes. It never struck me try try double quotes around the
> timezone argument. I'm shocked
On Wed, Jul 6, 2022 at 9:49 AM Bryn Llewellyn wrote:
> adrian.kla...@aklaver.com wrote:
>
> Not sure what your point is?
>
>
> Try these two:
>
>
>
>
>
>
> *set timezone = 'America/New_York';show timezone;set timezone =
> "America/New_York";show timezone;*
> Neither causes an error. The "show",
On Tue, Jul 5, 2022 at 11:12 AM Bryn Llewellyn wrote:
> The section "Writing SECURITY DEFINER Functions Safely":
>
>
> https://www.postgresql.org/docs/current/sql-createfunction.html#id-1.9.3.67.10.2
>
> explains the risk brought if a bad actor creates an object that preemps
> what the developer
On Tue, Jul 5, 2022 at 12:13 PM Tom Lane wrote:
> Bryn Llewellyn writes:
> > Thanks, all, for your replies. I'd assumed that the arguments of "set
> search_path" had to be SQL names. so I tried "". But that caused an error.
> I didn't try the ordinary empty string because I'd assumed that, as
On Tue, Jul 5, 2022 at 5:20 PM Tom Lane wrote:
> "David G. Johnston" writes:
> > In passing, the authentication error examples use the phrase
> > "database user name" in a couple of locations. The word
> > database in b
On Tue, Jul 5, 2022 at 11:05 AM Adrian Klaver
wrote:
> On 7/5/22 10:56 AM, shashidhar Reddy wrote:
> > Down time 10 to 15 hrs
> > Hardware specs are also not sure for now as it is client machine.
>
> This is going to be a difficult task for the following reasons:
>
> In other words there is
On Mon, Jul 4, 2022 at 4:03 PM Rhys A.D. Stewart
wrote:
>
> I have a trigger that is attached to several different tables. In the
> trigger function I retrieve a single row and I want the info from a
> specific column. This column is dependent on the table in question.
>
> The only workaround I
On Fri, Jul 1, 2022 at 7:58 AM Peter Geoghegan wrote:
> On Fri, Jul 1, 2022 at 6:01 AM Robert Haas wrote:
> > What would probably help more is adding something like this to the
> > error message:
> >
> > HINT: column "b" could refer to any of these relations: "foo", "excluded"
> >
> > That
On Thu, Jun 30, 2022 at 2:31 PM Peter Geoghegan wrote:
> On Thu, Jun 30, 2022 at 2:07 PM David G. Johnston
> wrote:
> > Current:
> > "The SET and WHERE clauses in ON CONFLICT DO UPDATE have access to the
> > existing row using the table's name (or an a
On Thu, Jun 30, 2022 at 1:43 PM Robert Haas wrote:
> On Thu, Jun 9, 2022 at 11:40 AM David G. Johnston
> wrote:
> > As one cannot place excluded in a FROM clause (subquery) in the
> > ON CONFLICT clause referring to it as a table, ...
>
> Well, it would be
On Thursday, June 30, 2022, Laurenz Albe wrote:
> On Thu, 2022-06-30 at 16:40 +0530, eswar reddy wrote:
> > Hi sir, I am getting below error for the past 3 month's plz can suggest
> how to resolve this issue.
> >
> > PostgreSQL 9.6 version and Linux redhat 7.2 efm 4.1 plz
> >
> > Fatel:
On Wed, Jun 29, 2022 at 5:03 PM Bryn Llewellyn wrote:
>
> *Meanwhile. I'll appeal for some pointers to what I should read:*
> I *had* understood that the SQL that a user-created subprogram issues (at
> least for "language sql" and "language plpgsql") is implicitly prepared.
> But I've no idea
On Wednesday, June 29, 2022, Bryn Llewellyn wrote:
>
> When I drop the first link, f1() in the chain of "immutable" functions, I
> see that I cannot invoke f(2) because it now complains that f1() doesn't
> exist. This surprises me because, after all, the result of f2() is now
> cached (at least
On Tuesday, June 28, 2022, Bryn Llewellyn wrote:
>
> DISCARD PLANS is unsafe in a multi-user concurrent scenario. The doc says
> explicitly that its scope is just the single session. And it's easy to show
> the danger by using my testcase manually, step by appropriate step, with
> two concurrent
On Tue, Jun 28, 2022 at 7:03 PM Christophe Pettus wrote:
>
>
> > On Jun 28, 2022, at 18:41, Bryn Llewellyn wrote:
> > Should I simply understand that when I have such a dynamic dependency
> chain of "immutable" functions, and should I drop and re-create the
> function at the start of the chain,
On Mon, Jun 27, 2022 at 11:25 AM Dean Rasheed
wrote:
> On Mon, 27 Jun 2022 at 16:12, Julien Rouhaud wrote:
> >
> > It doesn't play that well if you have something called subquery though:
> >
> > [example that changes a user-provided alias]
> >
> > While the output is a valid query, it's not
On Sunday, June 26, 2022, WR wrote:
>
> I made some test with pgadmin. Pgadmin (5.2) also reports this error now.
> And it doesn't matter if standard_conforming_strings is on or off.
>
>
> SET standard_conforming_strings = off;
>
> INSERT INTO public.oned_figures VALUES (1, 'Figure_Wolle1', 476,
Thank you for the review.
On Thu, Jun 23, 2022 at 5:35 AM Simon Riggs
wrote:
> On Thu, 9 Jun 2022 at 16:41, David G. Johnston
> wrote:
>
> "The name to give to the new savepoint. The name may already exist,
> + in which case a rollback or release to th
On Friday, June 24, 2022, Gurjeet Singh wrote:
> On Fri, Jun 24, 2022 at 4:13 PM Andres Freund wrote:
> > On 2022-06-25 00:08:13 +0200, Hannu Krosing wrote:
>
> > > 3) should this be back-patched (we can provide batches for all
> > > supported PgSQL versions)
> >
> > Err, what?
>
> Translation:
On Fri, Jun 24, 2022 at 4:13 PM Andres Freund wrote:
> Hi,
>
> On 2022-06-25 00:08:13 +0200, Hannu Krosing wrote:
> > Currently the file system access is controlled via being a SUPREUSER
> > or having the pg_read_server_files, pg_write_server_files and
> > pg_execute_server_program roles. The
On Fri, Jun 24, 2022 at 3:08 PM Hannu Krosing wrote:
>
> 1) would it be enough to just disable WRITING to the filesystem (COPY
> ... TO ..., COPY TO ... PROGRAM ...) or are some reading functions
> also potentially exploitable or at least making attackers life easier
> ?
>
I would protect read
On Fri, Jun 24, 2022 at 1:19 PM Robert Haas wrote:
> On Mon, Jun 6, 2022 at 7:41 PM Stephen Frost wrote:
> >
> > In terms of how that's then used, yeah, it's during REVOKE because a
> > REVOKE is only able to 'find' role authorization descriptors which match
> > the triple of role revoked,
On Thu, Jun 9, 2022 at 4:30 PM Jacob Champion
wrote:
> On Wed, Jun 8, 2022 at 9:58 PM Michael Paquier
> wrote:
>
> > One
> > interesting case comes down to stuff like channel_binding=require
> > require_auth="md5,scram-sha-256", where I think that we should still
> > fail even if the server
On Wed, Jun 22, 2022 at 12:11 PM Ibrar Ahmed wrote:
> On Thu, Jun 23, 2022 at 12:01 AM Tom Lane wrote:
>
>> Robert Haas writes:
>> > On Jun 2, 2009, at 9:41 AM, Simon Riggs wrote:
>> >> You're right that the number of significant digits already exceeds the
>> >> true accuracy of the
On Wed, Jun 22, 2022 at 9:28 AM Tom Lane wrote:
> Joe Conway writes:
> > On 6/22/22 11:52, Tom Lane wrote:
> >> I think a case could be made for ONLY returning non-null when authn_id
> >> represents some externally-verified identifier (OS user ID gotten via
> >> peer identification, Kerberos
On Tue, Jun 21, 2022 at 6:49 AM Aleksander Alekseev <
aleksan...@timescale.com> wrote:
> Hi David,
>
> > It's basically a glorified cross-reference. I didn't dislike directing
> the reader to the internals section enough to try and establish a better
> location for the main content.
>
> One
On Tue, Jun 21, 2022 at 6:33 AM Aleksander Alekseev <
aleksan...@timescale.com> wrote:
> Hi David,
>
> > Per discussion here:
> >
> >
> https://www.postgresql.org/message-id/163636931138.8076.5140809232053731248%40wrigleys.postgresql.org
> >
> > We can now easily document the array_length
On Wed, Jun 1, 2022 at 7:05 AM Peter Eisentraut <
peter.eisentr...@enterprisedb.com> wrote:
> On 31.05.22 22:12, David G. Johnston wrote:
> > Anything I should be doing differently here to get a bit of
> > reviewer/committer time on these? I'll add them to the commitfe
On Sun, Jun 19, 2022 at 2:31 PM Bryn Llewellyn wrote:
> It would be foolish, therefore, to define the target table for
> "insert-select" using "CTAS where false".
>
SQL is a strongly typed language where the structure of the query output is
determined without any consideration of whether said
On Sun, Jun 19, 2022 at 12:06 PM Дмитрий Иванов
wrote:
> Good afternoon.
> I have a query parser question. If there are two kinds of queries using an
> indexed field. In this case, one view is limited to this field, the second
> one uses a number of fields included in the index by the include
On Thu, Jun 16, 2022 at 8:28 PM Bryn Llewellyn wrote:
>
> *Back to NULLs...*
>
> Your code examples ran without error and produced the results that you
> described. I do understand the fact that, on its face, the NULLs in the
> two cases arise for different reasons. But this (still) seems to me
On Wed, Jun 15, 2022 at 11:23 PM Mark Dilger
wrote:
>
> > On Jun 15, 2022, at 8:50 PM, David G. Johnston <
> david.g.johns...@gmail.com> wrote:
> >
> > On Wed, Jun 15, 2022 at 8:18 PM Andres Freund
> wrote:
> > > If a simple callback like
> >
On Wed, Jun 15, 2022 at 11:07 PM Bryn Llewellyn wrote:
> This is what the doc promises. But how can you see it as anything but a
> bug? The subquery evaluates to "null", and only then is the attempt made to
> create a new row which self-evidently violates the domain's constraint. How
> is it any
On Wed, Jun 15, 2022 at 8:51 PM Michael Paquier wrote:
> On top of that
> default_table_access_method is user-settable.
>
>
FWIW this proposal acknowledges that and basically leverages it to the
hilt, turning it into something like search_path. I strongly dislike the
idea of any workflow that
On Wed, Jun 15, 2022 at 8:18 PM Andres Freund wrote:
> > If a simple callback like
> > relation_supports_cluster(Relation rel) is too simplistic
>
Seems like it should be called:
relation_supports_compaction[_by_removal_of_interspersed_dead_tuples]
Basically, if the user tells the table to
On Wednesday, June 15, 2022, Bryn Llewellyn wrote:
> I’ve copied a self-contained testcase below. Is the error that the "as
> intended" test causes due to a known limitation—or even a semantic dilemma
> that I'm failing to spot? Or might it be due to a bug?
>
I read the note in create domain as
On Mon, Jun 13, 2022 at 11:01 AM Robert Haas wrote:
> Some
>
syntax would be a bit different on the new releases and that would
> unlock some new options we don't currently have, but there's no
> behavior that you can get today which you wouldn't be able to get any
> more under this proposal.
>
On Sun, Jun 12, 2022 at 2:47 PM Josh wrote:
>
> This was only possible because I was dealing with arrays though, and an
> operation such as `in (select unnest...)` can be easily converted to `=
> any(...)`. However for the general case,
In the general case you don't have subqueries inside join
On Fri, Jun 10, 2022 at 3:40 AM PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/14/sql-copy.html
> Description:
>
> When copying a csv file into a table, ifthere is a string missing a double
> quote in
On Fri, Jun 10, 2022 at 9:38 AM Rama Krishnan wrote:
> I am want to delete old records using function so my senior has function
> like below but I want to get response of this particular inside query
> wheter it is successful or failure
>
If it doesn't error, it was successful. That is
Hi,
Per discussion here:
https://www.postgresql.org/message-id/163636931138.8076.5140809232053731248%40wrigleys.postgresql.org
We can now easily document the array_length behavior of returning null
instead of zero for an empty array/dimension.
I added an example to the json_array_length
Hi.
The fact that one transaction will wait on another if they are trying to
claim the same unique value is presently relegated to a subchapter of the
documentation where the typical reader will not even understand (rightly
so) the main chapter's title. This has prompted a number of questions
On Tue, Jun 7, 2022 at 5:26 PM Bruce Momjian wrote:
> On Tue, Jun 7, 2022 at 08:00:16PM -0400, Tom Lane wrote:
> > Bruce Momjian writes:
> > > +not occur at certain isolation levels;
> higher
> >
> > The docs toolchain is not gonna like that.
>
> You are correct. I should have tested,
On Tue, May 17, 2022 at 4:57 AM alias wrote:
>
> My thought process:
>
>> update = delete + insert.
>> so * create policy emp_upd on emp for update to public using (true); *should
>> be ok for updating every row, let insert policy handle new row
>> *. *
>> since there is only one
On Tue, May 24, 2022 at 7:42 AM Tom Lane wrote:
> I wrote:
> > Perhaps this should be documented more clearly, but it's not obviously
> > wrong. If the domain declaration doesn't include an explicit COLLATE
> > then casting to the domain doesn't create an explicit collation
> > requirement.
Per suggestion over on -docs:
https://www.postgresql.org/message-id/bl0pr06mb4978f6c0b69f3f03aebed0fbb3...@bl0pr06mb4978.namprd06.prod.outlook.com
David J.
0001-doc-Move-enum-storage-size-to-top-of-section.patch
Description: Binary data
Hi,
Reposting this to its own thread.
https://www.postgresql.org/message-id/flat/CAKFQuwby1aMsJDMeibaBaohgoaZhivAo4WcqHC1%3D9-GDZ3TSng%40mail.gmail.com
doc: make unique non-null join selectivity example match the prose
The description of the computation for the unique, non-null,
Hi.
Reposting this on its own thread.
https://www.postgresql.org/message-id/flat/CAKFQuwby1aMsJDMeibaBaohgoaZhivAo4WcqHC1%3D9-GDZ3TSng%40mail.gmail.com
The default database name is just the user name, not the
operating-system user name.
In passing, the authentication error examples
Hi.
Reposting this on its own thread.
https://www.postgresql.org/message-id/flat/CAKFQuwby1aMsJDMeibaBaohgoaZhivAo4WcqHC1%3D9-GDZ3TSng%40mail.gmail.com
Per discussion on -general the documentation for the
ALTER ROUTINE ... DEPENDS ON EXTENSION and DROP EXTENSION doesn't
clearly
On Thu, Jun 9, 2022 at 8:36 AM David G. Johnston
wrote:
> Hi,
>
> Reposting this on its own thread.
>
>
> https://www.postgresql.org/message-id/flat/CAKFQuwby1aMsJDMeibaBaohgoaZhivAo4WcqHC1%3D9-GDZ3TSng%40mail.gmail.com
>
> Presently, the open item seems to be whet
Hi,
Reposting this on its own thread.
https://www.postgresql.org/message-id/flat/CAKFQuwby1aMsJDMeibaBaohgoaZhivAo4WcqHC1%3D9-GDZ3TSng%40mail.gmail.com
As one cannot place excluded in a FROM clause (subquery) in the
ON CONFLICT clause referring to it as a table, with plural rows
Hi,
Reposting this on its own thread.
https://www.postgresql.org/message-id/flat/CAKFQuwby1aMsJDMeibaBaohgoaZhivAo4WcqHC1%3D9-GDZ3TSng%40mail.gmail.com
Presently, the open item seems to be whether my novelty regarding the
reworked example is too much.
David J.
On Wed, Jun 8, 2022 at 7:29 AM Virender Singla
wrote:
> but I still expect Postgres to save us from such data inconsistencies
> issues by using early binding for functional Indexes.
>
Well, if the functions you are writing are "black boxes" to PostgreSQL this
expectation seems unreasonable.
On Tue, Jun 7, 2022 at 4:51 PM Bruce Momjian wrote:
> On Tue, Jun 7, 2022 at 02:40:41PM -0700, David G. Johnston wrote:
> > On Tue, Jun 7, 2022 at 2:07 PM Bruce Momjian wrote:
> >
> >
> >
> > How is this, attached?
> >
> >
> >
> >
On Tue, Jun 7, 2022 at 2:07 PM Bruce Momjian wrote:
>
>
> How is this, attached?
>
>
Works for me.
Capital "S" in Standard as a proper name? (mind grepping this to see how
consistent we are one way or the other, I'm not setup for that at the
moment)
David J.
n Tue, Jun 7, 2022 at 1:30 PM PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/14/sql-insert.html
> Description:
>
> It looks like INSERT INTO ... RETURNING allows defining a target for the
> returned
On Sun, Jun 5, 2022 at 4:06 PM Frank Finner wrote:
> If you use -U with psql, the connection must not try to use method "peer"
> (which means "use the system user with this name", but also means "You must
> be logged in with the system user corresponding to the postgresql user"),
> but some kind
On Sat, Jun 4, 2022 at 7:50 AM Tom Lane wrote:
> Robert Stanford writes:
> > Can anyone suggest an elegant way to coalesce consecutive rows so only
> the
> > first start time and last end time for each group of events (by input) is
> > returned.
>
> Window functions don't change the number of
On Fri, Jun 3, 2022 at 6:41 PM Bryn Llewellyn wrote:
>
>
>
>
> *declare j1 constant jsonb not null := '{"x": 42, "y":
> null}'; j2 constant jsonb not null := '{"x": 42 }';*
>
> *(j1->>'y' is null) *
>
This produces a JSON Null which when asked for as a text
On Thursday, June 2, 2022, jian he wrote:
>
> https://www.postgresql.org/docs/current/monitoring-stats.
> html#MONITORING-PG-STAT-DATABASE-VIEW
>
>> xact_commit bigint
>>
>> Number of transactions in this database that have been committed
>>
> In
On Wed, Jun 1, 2022 at 7:05 AM Peter Eisentraut <
peter.eisentr...@enterprisedb.com> wrote:
> On 31.05.22 22:12, David G. Johnston wrote:
> > Anything I should be doing differently here to get a bit of
> > reviewer/committer time on these? I'll add them to the commitfe
ipped even with the couple of bad bugs being worked on.
Thank you!
David J.
On Fri, Apr 29, 2022 at 6:52 AM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> Updated status of the set.
>
> On Wed, Apr 20, 2022 at 5:59 PM David G. Johnston <
> david.g.johns...@gmail.com
On Tuesday, May 31, 2022, Praneel Devisetty
wrote:
>
> Initially it was processing 1000 tables per minute. Performance is
>> gradually dropping and now after 24 hr it was processing 90 tables per
>> minute.
>>
>
That seems like a fairly problematic metric given the general vast
disparities in
On Tuesday, May 31, 2022, PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/14/sql-createextension.html
> Description:
>
> I'm trying to add an extension to two schemas that I have in my DB.
>
> steps:
>
>
On Sat, May 28, 2022 at 9:35 AM Roffild wrote:
> Docker is now the DevOps standard. It's easier to build an image for
> Docker and run the site with one command.
>
> But the volume mount has a limitation with chmod 755. I don't want to
> write the database directly to the container.
>
> The
On Fri, May 27, 2022 at 9:19 AM Andrus wrote:
> Product type table contains product types. Some ids may missing :
>
>
> create table artliik (liiginrlki char(3) primary key);
>
As an aside, don't use the "character" data type:
On Thursday, May 26, 2022, Matthias Apitz wrote:
>
> Is there any way to get with the old CTID to the row, for example with
> the old CTID to the new one which the row now has after the update of the
> row?
>
>
No, there is no link between old and new in the main table.
David J.
On Wednesday, May 25, 2022, Rich Shepard wrote:
>
> I'm trying to insert 15 new rows to that table by inserting all columns
> except the first one..
That…
>
> person_nbr 683 is not in any row to be inserted.
Implies that.
>
> I was under the impression that the person_nbr for the new
On Wednesday, May 25, 2022, Bryn Llewellyn wrote:
> Forgive me if this is the wrong address.
>
> I went to https://postgresteam.slack.com/join/signup but found that my
> email address has an unknown domain. It says "Don’t have an email address
> from one of those domains? Contact the workspace
On Wednesday, May 25, 2022, Carsten Klein wrote:
>
>
>> pg_lsclusters is not part of core Postgres, and neither is this
>> --cluster option you mention. I'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
On Wednesday, May 25, 2022, Rob Sargent wrote:
> On 5/25/22 08:20, Tom Lane wrote:
>
> Rob Sargent writes:
>
> Just wondering if I've bumped into some security issue.
> I'm somewhat surprised that "grant connect to database to
> " appears to be stored "by name"?
>
> I think you are
On Wednesday, May 25, 2022, Japin Li wrote:
>
> Hi,
>
> Today, I try to use repeat() to generate 1GB text, and it occurs invalid
> memory
> alloc request size [1]. It is a limit from palloc(), then I try to reduce
> it,
> it still complains out of memory which comes from enlargeStringInfo()
>
On Wednesday, May 25, 2022, jian he wrote:
>
> I personally feel wording *non-default* may not be that correct. Because
> if the column is text then it automatically at least has default collation.
>
Non-default means “a value that is not the default value”.
David J.
Please don’t top-post.
On Tuesday, May 24, 2022, jian he wrote:
>
> Otherwise, all input expressions must have the same implicit collation
>> derivation or the default collation. If any non-default collation is
>> present, that is the result of the collation combination. Otherwise, the
>>
On Monday, May 23, 2022, jian he wrote:
> CREATE DOMAIN testdomain AS text;
>
> --asume the default collation is as per show LC_COLLATE;
>
> – on my pc, it is C.UTF-8.
>
> --So the testdomain will be collation "C.UTF-8"
>
>
> => \d collate_test1
>
> Table
On Sunday, May 22, 2022, Saladin wrote:
>
> The output i expected:
> pg_largeobject_metadata and pg_largeobject in both database A and database
> B should have rows.Shouldn't only in database A.So, i can use large object
> functions
> to operate large_objectin remote table or foreign table.
>
On Sat, May 21, 2022 at 4:38 PM Kip Cole wrote:
> I’m trying to cast a string value to a collation name without success. My
> suspicion is this isn’t possible
> based upon the error message.
You cannot cast between a token that interpreted as a literal and one that
is interpreted as a name.
On Sat, May 21, 2022 at 10:04 AM Ranier Vilela wrote:
> Em sáb., 21 de mai. de 2022 às 13:13, Tom Lane
> escreveu:
>
>> Ranier Vilela writes:
>> > Em sáb., 21 de mai. de 2022 às 12:05, Tomas Vondra <
>> > tomas.von...@enterprisedb.com> escreveu:
>> >> That's a quite bold claim, and yet you
901 - 1000 of 4977 matches
Mail list logo
