Hello all
A while ago, our company had an Postgres DB that was Hacked login db to
modify data
found that pg_hba.conf is not work
Any ip, user can log in to DB
1. The rules in pg_hba.conf are almost invalid
2. pg_hba.conf is only useful for METHOD = trust
3. check SHOW hba_file; the file location
shing dong writes:
> 1. The rules in pg_hba.conf are almost invalid
> 2. pg_hba.conf is only useful for METHOD = trust
> 3. check SHOW hba_file; the file location is correct
> 4. select * from pg_hba_file_rules; checked is correct
> 5.DB version : PostgreSQL 10.19 on x86_64-pc-linux-gnu, compi
> pavel.steh...@gmail.com wrote:
>
>> b...@yugabyte.com wrote:
>>
>> I’m still hoping that I might get some pointers to whitepapers or blog posts
>> that expand on those bullets that I quoted from the PG doc: «Instead of
>> packages, use schemas to organize your functions into groups.» and «Si
út 21. 12. 2021 v 19:28 odesílatel Bryn Llewellyn
napsal:
> *pavel.steh...@gmail.com wrote:*
>
>
> *b...@yugabyte.com wrote:*
>
> I’m still hoping that I might get some pointers to whitepapers or blog
> posts that expand on those bullets that I quoted from the PG doc: «Instead
> of packages, us
On Tue, Dec 21, 2021 at 11:50 AM Pavel Stehule
wrote:
> I wrote about it. Did you read this article?
>
> https://okbob.blogspot.com/2018/02/schema-variables.html
>
> The goals of this project:
>
>- fast non transactional non persistent (session based) storage,
>
> Would there be statistics th
út 21. 12. 2021 v 19:58 odesílatel Michael Lewis
napsal:
> On Tue, Dec 21, 2021 at 11:50 AM Pavel Stehule
> wrote:
>
>> I wrote about it. Did you read this article?
>>
>> https://okbob.blogspot.com/2018/02/schema-variables.html
>>
>> The goals of this project:
>>
>>- fast non transactional n
On 21/12/2021, at 10:25 AM, Tom Lane wrote:
> Not quite like that. Look into nodeAgg.c, which solves a similar problem
> for the transvalues themselves with code like
>
>/* forget the old value, if any */
>if (!oldIsNull && !pertrans->inputtypeByVal)
>pfre
Hi: I need a sanity check (brainstorming) before I jump into coding
something that might have a better solution known to a community like this
one. Here's the situation...
To begin with... PG 11.5 on linux.
Some code (nature unimportant to this discussion) generates a lot (a lot)
of data and stu
Could you use the SQLite FDW - https://github.com/pgspider/sqlite_fdw ?
Steve
On Wed, Dec 22, 2021 at 1:27 PM David Gauthier
wrote:
> Hi: I need a sanity check (brainstorming) before I jump into coding
> something that might have a better solution known to a community like this
> one. Here's
On Tuesday, December 21, 2021, David Gauthier
wrote:
>
> OK, you get the picture. I'm all ears :-) And thanks in advance for any
> suggestions !
>
This is basically a variant of “should I store images in the database” but
the content sizes involved are insanely high compared to most images.
Ex
*DEAR TOM*
just one PG instance in host
I did an experiment
When I remove pg and reinstall pg, the function of pg_hba is working
,represent that the location of pg_hba is right
- remove
yum remove postgresql*
--- install
yum -y install
https://download.postgresql.org/pub/repos/yum/repor
Please don't top post; the convention here is to inline or bottom post and
trim unnecessary quoting.
On Tue, Dec 21, 2021 at 9:24 PM shing dong wrote:
>
> - remove
> yum remove postgresql*
>
> --- install
> yum -y install
> https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/p
I'll have to read more about sqlite_fdw. Thanks for that Steve !
Each SQLite isn't that big (billions of records), more like 30K records or
so. But there are lots and lots of these SQLite DBs which add up over time
to perhaps billions of records.
This is for a big corp with an IT dept. Maybe I
On Tue, Dec 21, 2021 at 10:06 PM David Gauthier
wrote:
> I'll have to read more about sqlite_fdw. Thanks for that Steve !
>
> Each SQLite isn't that big (billions of records), more like 30K records or
> so. But there are lots and lots of these SQLite DBs which add up over time
> to perhaps billi
14 matches
Mail list logo