byme@byme.email schreef op ma 02-10-2023 om 16:19 [+]:
>
>
> Is there a possibility the pg_stat_statements will be improved with
> handling IN? This problem makes it so much less useful right now.
not sure what the question is,
but if you change pg_stat_statements with another view/table,
Tom Lane schreef op ma 02-10-2023 om 10:21 [-0400]:
> Wim Bertels writes:
> > * but if you put more than 1 option, then it doesn't?:
>
> > #psql
> > postgresql://myuser@myserver/mydb?connect_timeout=10_session
> > _attrs=any
>
> Maybe you forgot
Hello,
can anyone confirm this?:
* connections with at most 1 option after the ?-mark sign work:
like
#psql postgresql://myuser@myserver/mydb?connect_timeout=10
or
#psql postgresql://myuser@myserver/mydb?target_session_attrs=any
* but if you put more than 1 option, then it doesn't?:
#psql
Joe Conway schreef op vr 09-06-2023 om 09:16 [-0400]:
> On 6/8/23 22:17, Pat Trainor wrote:
> > I need to have a very large matrix to maintain & query, and if not
> > (1,600 column limit), then how could such data be broken down to
> > work?
>
> 100,000 rows *
> 100,000 columns *
> 8 bytes
Thomas Kellerer schreef op vr 17-03-2023 om 11:21 [+0100]:
> Wim Bertels schrieb am 17.03.2023 um 11:05:
> > what would be the general idea: "easily" convert an hierarchical
> > structure like json or xml to a table; for example creating columns
> > by
> > app
Hello,
in python pandas there is for example a json_normalize function,
i didn't find something similar or better in postgresql?
what would be the general idea: "easily" convert an hierarchical
structure like json or xml to a table; for example creating columns by
appending the key-names when
Hello Giovanni,
it depends,
do you know a truly open source os without proprietary blobs for firmware or
device drivers?
Debian used to try to make a clear separation in this with 'main' being the
default section when installing,
unfortunately this practically no longer applies to proprietary
sivapostg...@yahoo.com schreef op ma 22-08-2022 om 07:29 [+]:
>
> ALTER TABLE public.tx_barcode_stock
> ADD CONSTRAINT "tx_barcode_stock_CK1" CHECK
> ( (branchcode = '1'::bpchar and barcodeitem = 'Y'::bpchar and
> closingstock >= 0::numeric) Or (branchcode = '1' and barcodeitem =
>
Perry Smith schreef op ma 15-08-2022 om 08:49 [-0500]:
> I like to have what I call “baby sitting” messages such as “Completed
> 15 out of 1023”. To do this, I need the number of results a query
> returns but I also need the results.
>
> Currently I’m doing this with two queries such as:
>
>
Laurenz Albe schreef op vr 25-02-2022 om 10:33 [+0100]:
> On Thu, 2022-02-24 at 18:16 +0100, Wim Bertels wrote:
> This was interpreted as if you had entered it in a single line:
>
> \set x 1 select :x
>
> So "x" is now "1select1;".
yes
>
Hello,
a quick question about
https://www.postgresql.org/docs/current/app-psql.html
and the \set option
it seems that \set does not interpret an 'enter' interactively the same
as an 'enter' in a short script made with \e
###
* case 1:
postgres=# \set x 1
postgres=# select :x;
?column?
hex 2 ascii
SQL Padawan schreef op wo 01-12-2021 om 18:37 [+]:
> \x6461
--
mvg,
Wim Bertels
--
https://coronalert.be
Lector
UC Leuven-Limburg
--
Truth is the most valuable thing we have -- so let us economize it.
-- Mark Twain
Is it possible that this is mainly an emotional discussion?
Raymond Brinzer schreef op di 14-09-2021 om 02:39 [-0400]:
> Many languages are awesome. I'm always astonished at what great
> things people have come up with, over the years; it's been a
> wonderfully fertile field. We would certainly
ws=3 width=4) (actual time=0.001..0.003
rows=7 loops=3503)
Index Cond: ("AlbumId" = "Album"."AlbumId")
Filter: ("Milliseconds" < t."Milliseconds")
Rows Removed by Filter:
one table
> name called sports I want to import data from A into B instances I
> found foreign data wrapper is the best solution when the table is
> huge here I have doubt is it foreign data wrapper and foreign tables
> are same?
>
>
> Thanks
>
> Rama Krishnan
--
mvg,
Daniel Verite schreef op do 03-12-2020 om 16:32 [+0100]:
> Wim Bertels wrote:
>
> > but interactively this doesn't seem to work
>
> Interactively something like this might do the job:
>
> $ PSQL_HISTORY=/tmp/queries.txt psql -L /tmp/logfile.txt
>
&
Daniel Verite schreef op do 03-12-2020 om 15:18 [+0100]:
> Wim Bertels wrote:
>
> > * one pipe (or..) to a file which only contains the statements
> > (queries) history (and not the output)
> > * another pipe (or..) to a file which only contains the output
Hello,
psql shows (the queries and) the output,
there are for example the -L option and echo_queries option
is there a way to run psql so that:
* inside psql there are no surprises :) (ignore this line:)
* one pipe (or..) to a file which only contains the statements
(queries) history (and not
First thougt: A general solution that you could use is wireshark.
For example : Search for wireshark ssl traffic
Susan Joseph schreef op September 3, 2020 10:54:36 AM
UTC:
>OK, I understand I was just hoping someone could confirm that my
>settings are correct.
>I didn't come across an error
elect
> statements.
>
> Thanks.
>
> Tiff
--
mvg,
Wim Bertels
--
Lector
UC Leuven-Limburg
--
There is no hunting like the hunting of man, and those who have hunted
armed men long enough and liked it, never care for anything else thereafter.
-- Ernest Hemingway
ps%3A%2F%2Fwww.scribd.com%2Fuser%2F270125049%2FTeo-En-Mingdata=02%7C01%7Cwim.bertels%40ucll.be%7Cb58a22dd7cca44dbff4f08d7d4a8c9d5%7Ce638861b15d94de6a65db48789ae1f08%7C0%7C0%7C637211694717781909sdata=Ug%2BqnOPc5bB4g1LrECXLIz8EOUKlvdDXF10%2BcUTfxTI%3Dreserved=0
>
> -END EMAIL SIGNATURE
idence) as
> aggstat,statcount,short_name_en from stats_residence where
> aggstat>some_number;
>
> But as I soon discovered that's not valid syntax! Hence ideas welcome
> from those smarter than me.
>
> Thanks !
>
> Laura
>
>
--
mvg,
Wim Ber
lease don't hesitate to ask me.
>
> Tia and rgs,
>
> Pól...
>
>
--
mvg,
Wim Bertels
--
Lector
UC Leuven-Limburg
--
The human race has one really effective weapon, and that is laughter.
-- Mark Twain
Using the datatype citext might be an alternative solution
Igal Sapir schreef op October 8, 2019 10:51:52 PM UTC:
>I am trying to test a simple case insensitive comparison. Most likely
>the
>collation that I chose is wrong, but I'm not sure how to choose the
>correct
>one (for English/US?).
Or
CREATE TABLE t();
SELECT *
FROM t;
Van: Tatsuo Ishii
Verzonden: maandag 7 oktober 2019 10:00
Aan: pgsql-gene...@postgresql.org
Onderwerp: RowDescription message
According to the manualof RowDescription message
Steve Haresnape schreef op vr 15-03-2019 om 12:06 [+1300]:
> I'm porting a sql server database to postgresql 9.6. My camelCase
> identifiers are having their humps removed. This is disconcerting and
> sad.
the SQL ISO defines exactly this behaviour (as you note),
so this is be expected
26 matches
Mail list logo
