donderdag 31 maart 2022

tnsping sqlnet.ora not listing

Via OraFAQ Forum - RDF feed by patdev
Hello,

i am kind of confuse on the issue of tnsping.

when i do tnsping dbname:

it resolves fine but it does not list parameter file: sqlnet.ora Please help on that...

used parameter file: does not list

[user@servernam dbhome_1]$ tnsping dbname

TNS Ping Utility for Linux: Version 12.1.0.2.0 - Production on 31-MAR-2022 10:45:33

Copyright (c) 1997, 2014, Oracle. All rights reserved.

Used parameter files:


Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = servername)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = dbname)))
OK (0 msec)

New article matched for in your Blogger! rule

Testing Wide Production 2020
By

dinsdag 29 maart 2022

How to Create a Static Website Using Amazon S3

s3-static-website.jpg

Amazon Simple Storage Service (S3) is a web service offered by Amazon Web Services (AWS) for storing and access to objects via the internet. S3 offers websites, web services, and mobile applications the ability to upload data and store it on its servers. In this guide, we will create and configure a simple static website using Amazon S3.

New article matched for in your Blogger! rule

Testing Wide Production 2020
By

AWS Postgres RDS vs Aurora PostgreSQL?

Via PostgreSQL by /u/sharadov

Which one would you pick for production workloads and why? I am asking the question from the perspective of performance, cost, support for Postgres extensions - which makes Postgres so powerful. Would like to get perspectives from folks who are currently using/have used them in production.

submitted by /u/sharadov
[link] [comments]

New article matched for in your Blogger! rule

Testing Wide Production 2020
By

zaterdag 26 maart 2022

Technisch Architect - De Staffing Groep - Den Haag

DICTU levert ICT en digitale diensten voor Ministerie EZK en een aantal andere ministeries. Ze zet haar kennis en ervaring in om de beleids- en organisatie…
Van De Staffing Groep - Wed, 23 Mar 2022 13:04:11 GMT - Toon alle vacatures in Den Haag

New article matched for in your Blogger! rule

Testing Wide Production 2020
By

vrijdag 25 maart 2022

[UPDATE] RSS Guard v4.2.1

scruQSXzZ.png

RSS Guard is a customizable, skinnable feed reader with a tabbed interface. It can fetch the most known feed formats, including RSS/RDF and ATOM and store them in a nested list, keyboard shortcuts, notification settings, gesture support and more.

Only available for 64-bit. Cross-platform, supporting a wide array of operating systems (Linux, OS X, *BSD and more).

pfc?d=UT3xtbGYFzA pfc?i=cKQ_CBtJftE:jei8Aa501fo:V_sGLiPBpW pfc?d=qj6IDK7rITs pfc?i=cKQ_CBtJftE:jei8Aa501fo:gIN9vFwOqv pfc?i=cKQ_CBtJftE:jei8Aa501fo:F7zB nMyn0L

New article matched for in your Blogger! rule

Testing Wide Production 2020
By

vrijdag 18 maart 2022

PG limitations with numerous index scan queries

Via PostgreSQL by /u/CacheMeUp

The following query takes >45 minutes on Postgresql 14, 64GB RAM, 8 cores CPU:

create table table_50M_rows_A (id varchar(16) primary key, c1 jsonb, c2 text /* 100-1025 characters */, c3 timestamp); create table table_50M_rows_B (id varchar(16) primary key, c2 text /* 100-1025 characters */, c3 timestamp); set work_mem='16384MB'; select id from table_50M_rows_A a where not exists (select from table_50M_rows_B b where a.id=b.id)

despite using index scan. The PK index is several GBs big but smaller than work_mem.

When implemented as a procedural code in Java, it is x10 faster (4 minutes), where the bottleneck is actually IO from the database:

var existing = new HashSet(); for (var id in "select id from table_50M_rows_B") existing.add(id); var diff = new ArrayList(); for (var id in "select id from table_50M_rows_A"){ if (!existing.contains(id)) diff.add   (id); }

The Java code uses also 8 cores.

It seems that the query engine fails to utilize the index as a hash-set (membership check). It seems to have challenges handling queries that involve small tasks but on numerous rows. This is despite being written in C and overall being highly optimized.

Is there a way to optimize such queries on Postgresql? I don't want to "re-invent the wheel".

​

Query plans:

No hints:

EXPLAIN select id from table_50M_rows_A a where not exists (select from table_50M_rows_B b where a.id=b.id); Gather (cost=3690212.14..5956357.34 rows=1 width=16) Workers Planned: 2 -> Parallel Hash Anti Join (cost=3689212.14..5955357.24 rows=1 width=16) Hash Cond: (a.id= b.id) -> Parallel Index Only Scan using x_table_a_id on table_50M_rows_A a (cost=0.56..1287666.41 rows=21855175 width=16) -> Parallel Hash (cost=3299770.03..3299770.03 rows=22403803 width=16) -> Parallel Seq Sca   n on table_50M_rows_B b (cost=0.00..3299770.03 rows=22403803 width=16)

set enable_seqscan=false

Gather (cost=1001.13..100945294.37 rows=1 width=16) Workers Planned: 2 -> Nested Loop Anti Join (cost=1.13..100944294.27 rows=1 width=16) -> Parallel Index Only Scan using x_table_a_id on table_50M_rows_A a (cost=0.56..1287666.41 rows=21855175 width=16) -> Index Only Scan using table_b_pkey on table_50M_rows_B b (cost=0.56..4.55 rows=1 width=16) Index Cond: (a.id=b.id)

​

submitted by /u/CacheMeUp
[link] [comments]

New article matched for in your Blogger! rule

Testing Wide Production 2020
By

vrijdag 4 maart 2022

Ansible : First Steps

site-media-image.png

This article presents the first steps to get you up and running with Ansible.

New article matched for in your Blogger! rule

Testing Wide Production 2020
By

dinsdag 1 maart 2022

pgwatch2 v1.9 Beta released and available for testing

pgwatch2-v1.9-Beta-Released_Twitter-FB-e

We want to announce that the beta release of pgwatch2 v1.9 is now available for download. This release contains previews of all features that will be available in the final release of pgwatch2 v1.9, though some details of the release could change before then.

You can find information about all of the new features and changes in pgwatch2 v1.9 within the release notes.

In the spirit of open-source software, we strongly encourage you to test the new features of pgwatch2 v1.9 on your systems to help us eliminate any bugs or other issues that may exist. While we don't advise you to run pgwatch2 v1.9.0-beta in your production environments, we encourage you to find ways to run your typical application workloads against this beta release.

pgwatch2 v1.9 Feature Highlights

New Features

It has been a long time since our previous release. And even though pgwatch2 v1.9 is not considered a major upgrade, there are a lot of impressive changes.

First of all, we have a new maintainer for pgwatch2. That's me, Pavlo Golub. I hope Kaarel Moppel, the author of pgwatch2, will still work on the project – but now without the extra burden of support and maintenance.

We've used the latest Go v1.17 for all binaries and Docker images.

We now have full PostgreSQL v14 support and support for the latest Grafana v8 visualization solution. For those who still use the previous versions of Grafana, we also added support for v7 and v6 dashboards.

To improve our CI/CD experience and automate some tasks, we've introduced three GitHub Actions in a series of planned workflows:

  • Release
  • CodeQL analysis
  • Close Stale Issues and PRs
  • The Release workflow will automatically build all artifacts, including Docker images, and publish the release.

CodeQL analysis stands guard over code security. It will thoroughly investigate each pull request and each push.

It's not a surprise that many issues are created for open-source projects which never get a follow-up contribution from the topic starter. We have enabled a Close Stale Issues and PRs workflow to keep up with the continuous storm of new issues and PRs. It will mark issues and PRs with no activity as stale, and eventually close them.

We added many more cool features, like new gatherer options, e.g. --try-create-listed-exts-if-missing. Or like new metrics for monitoring "wait_events".

Performance

We provided many code modifications to improve performance.

Prometheus-mode monitoring is now one of the essential optimizations.

We rewrote the gatherer code to skip tables without waiting for AccessExclusiveLock.

We've added a new --min-db-size-mb flag to ignore "empty" databases. It allows the gatherer to skip measures fetching for empty or for small-sized databases.

pgwatch2 v1.9 comes with fully redesigned connection pooling, which will hardly rely on sqlx.DB from now on.

Timeouts have been greatly increased for database and table size fetching – to 5min.

Metric fetching was made less disruptive by setting a short lock_timeout.

The new --no-helper-functions parameter allows you to skip metric definitions which rely on helper functions. This mode makes working with managed instances more fluid, with fewer errors in logs. It uses the SU or superuser version of a metric immediately when available, and not after the first failed call.

The new --emergency-pause-triggerfile flag aims to quickly shut down collectors. The main idea of the feature is to quickly free monitored databases and networks of any extra "monitoring effect" load.

Additional Features

You'll find many other new features and improvements in pgwatch2 v1.9. Some may be more important to your use case than those highlighted above. Please see the release notes for a complete list of new and changed features.

Testing for Bugs & Compatibility

The stability of each pgwatch2 v1.9 release significantly depends on the community's effort to test the upcoming version with your workloads and testing tools, in order to find bugs and regressions before pgwatch2 v1.9 becomes generally available. As this is a Beta, minor changes and bug fixes are still possible. Your feedback and testing will help determine the final tweaks on the new features, so please test as soon as possible. The quality of user testing helps decide when we can make an official release.

A list of open issues is publicly available in the pgwatch2 repository. You can report bugs using this form: https://github.com/cybertec-postgresql/pgwatch2/issues.

The post pgwatch2 v1.9 Beta released and available for testing appeared first on CYBERTEC.

New article matched for in your Blogger! rule

Testing Wide Production 2020
By
Abonneren op: Posts (Atom)