Ok, I'll check it out. Thank you.
On Sat, 30 Mar, 2024, 10:36 Julien Rouhaud, wrote:
> On Sat, Mar 30, 2024 at 12:47 PM arun chirappurath
> wrote:
> >
> > I have granted access to pg_read_all_stats and pg_read_allsettings to
> user..still they are not able to receive results from this query
On Sat, Mar 30, 2024 at 12:47 PM arun chirappurath wrote:
>
> I have granted access to pg_read_all_stats and pg_read_allsettings to
> user..still they are not able to receive results from this query.its
> empty..we can run SELECT * FROM pg_stat_statements alone..but not below
> statement..what
Dear all,
I have granted access to pg_read_all_stats and pg_read_allsettings to
user..still they are not able to receive results from this query.its
empty..we can run SELECT * FROM pg_stat_statements alone..but not below
statement..what could be the reason?
WITH statements AS (
SELECT * F
On 2024-03-30 05:53, Alexander Farber wrote:
I use the following postgresql.conf in my Dockerfile
( the full version at https://stackoverflow.com/a/78243530/165071 ),
when loading a 28 GByte large europe-latest.osm.pbf
Is anybody please able to spot any improvements I could
apply to the postg
On 3/29/24 15:36, David Gauthier wrote:
Ya, I kind of agree on the >1 DB connections not allowed. It
(perl/DBI) does allow for >1 active DB handles (objects). But of
course those handles/objects have different names and that's how to
work with the different ones (not a DB prefix like what
Hi Jason,
CIS benchmark is a good place to that.
https://www.cisecurity.org/benchmark/postgresql
Regards,
Flavious
On Fri, Mar 29, 2024 at 5:37 PM Jason Long wrote:
> Hello,
> There are many articles on the internet to secure PostgreSQL, but which
> one is valid and up-to-date!
>
> Please i
Hi:
I think your problem is in the Perl side more than in PostgreSQL's. When
you said you tried escaping with \, Did you mean *exactly* this?
"delete from \"thedb.v1\".theschem.thetab where col1 = 1"
I think this should work.
Or you can use single quotes to enclose the query, so that you
Hello,There are many articles on the internet to secure PostgreSQL, but which
one is valid and up-to-date!
Please introduce a suitable article.
Thank you.
Ya, I kind of agree on the >1 DB connections not allowed. It (perl/DBI)
does allow for >1 active DB handles (objects). But of course those
handles/objects have different names and that's how to work with the
different ones (not a DB prefix like what I have). Still, it accepted the
name in the sy
> On Mar 29, 2024, at 14:16, David Gauthier wrote
> I tried encapsulating the DB name in double quotes (no good), single quotes
> (still no good) escaping with '\' (no good), escaping with ".." (no good).
This is probably more about the string handling in the API you are using than
Postgre
On Fri, Mar 29, 2024 at 2:20 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Fri, Mar 29, 2024 at 2:16 PM David Gauthier
> wrote:
>
>> I tried encapsulating the DB name in double quotes (no good)
>>
>
> This is what the documentation says you are supposed to do for non-simple
> ide
On Fri, Mar 29, 2024 at 2:16 PM David Gauthier
wrote:
> I tried encapsulating the DB name in double quotes (no good)
>
This is what the documentation says you are supposed to do for non-simple
identifiers so you need to show your work to understand where you went
wrong.
David J.
Hi:
I have a DB named "thedb", which has a schema called "theschem" which has a
table called "thetab". In a perl/DBI script, I am able to work with the
table by referencing it as... "thedb.theschem.thetab" as in... "delete from
thedb.theschem.thetab where col1=1"
No problem (so far...)
New DB n
Good evening,
I use the following postgresql.conf in my Dockerfile
( the full version at https://stackoverflow.com/a/78243530/165071 ),
when loading a 28 GByte large europe-latest.osm.pbf
into PostgreSQL 16 with PostGIS extension:
echo "shared_buffers = 1GB">> $PGDATA/postgres
14 matches
Mail list logo
