Hello team,
I am trying to understand the parameter shared_memory_size. It is a static
parameter that reports the size of the shared memory area. Does that imply
that the value may change depending on the memory used by the server?
Regards,
Jayadevan
On Tue, Nov 12, 2024 at 7:47 PM Ron Johnson wrote:
> The documentation tells you, down in the Notes section.
>
> https://www.postgresql.org/docs/16/sql-createpublication.html
>
Thank you.
Hello all,
I am using PostgreSQL 16.4. I tried to set up logical replication with
"postgres" user and all worked fine. Then I created a new user
(my_replication) to be used for the purpose and couldn't figure out which
privileges are necessary. Initially I got an error like "ERROR: permission
de
Hi all,
We use PostgreSQL as. our primary data persistence layer and are looking
for a tool to document the database as well as capture additional info.
Looking for suggestions.
The tool should be able to scan the database (PostgreSQL) and generate a
list of entities and attributes and persist thi
When a user load a new table in the Postgres System? Can a script
> automatically detect it and run?
>
> Are you looking for Even triggers?
https://www.postgresql.org/docs/current/event-triggers.html
Regards,
Jay
On Wed, Oct 27, 2021 at 11:49 AM Julien Rouhaud wrote:
>
>
> Most likely you had a different version of the glibc or ICU libraries
> on the new system, which lead to your indexes on collatable datatypes
> partially corrupted. See https://wiki.postgresql.org/wiki/Collations
> for more details.
>
Hello all,
We moved our PostgreSQL database from one hosting provider to another using
pgbackrest. In the new environment, some comparison operations were
failing. The issue was fixed by running an update. But I am trying to find
out what would have happened.
select * from accounts where email
On Thu, Aug 19, 2021 at 11:41 AM Julien Rouhaud wrote:
>
> The value you see on pg_settings is the one that's selected for your
> current connection, based on the database/role you used.
>
> You can use \drds in psql to see the various configurations, or query
> the pg_db_role_setting table.
>
Th
On Wed, Aug 18, 2021 at 9:36 PM Bruce Momjian wrote:
> On Wed, Aug 18, 2021 at 09:34:08PM +0530, Jayadevan M wrote:
> > Hello all,
> >
> > A doubt on the setting 'log_statement'. Is it possible to set this at
> database
> > /user level?
>
> Sure, AL
Hello all,
A doubt on the setting 'log_statement'. Is it possible to set this at
database/user level?
I get 'all' when I try
select * from pg_settings where name = 'log_statement'
Does this mean all statements by any user on any database in that server
are getting logged? This is for auditing pur
>
> Using PostgreSQL 13.1
>
> I am new to PostgreSQL transitioning from Oracle. One of the many Oracle
> tricks I learned is that large inserts can be sped up by adding the direct
> path load hint /*+APPEND*/ . I am faced with having to perform many large
> inserts (100K->100M rows) in my Postgre
>
> So I’m looking for a way to identify if the refresh process is finished or
> if it’s still running - preferably without having to wait for timeout by
> querying a locked materialized view. But by e.g. using the system tables
> or otherwise.
>
>
>
> Can anybody suggest some pointers on how to
>
> We load large tables in some customer installation (some millions of rows)
> from file with:
>
> TRUNCATE TABLE tableName ;
> \COPY tableName FROM 'fileName' WITH ( DELIMITER '|' )
>
>
May be you could also make sure that loading actually stopped, by checking
the size of the data direct
On Sat, May 30, 2020 at 5:51 PM Paul Förster
wrote:
> Hi,
>
> I know, this list is not for this, but I just couldn't resist. Please
> forgive me.
>
> Being an Oracle DBA for two decades now (back then starting with Oracle
> 8.0.5) and only doing PostgreSQL since version 10.3, I feel compelled to
On Fri, Jan 31, 2020 at 3:22 PM Sandip Pradhan
wrote:
> Hi Ron,
>
> Thanks for your time.
>
> We are using the version 9.5.9.14.
>
May be you could try tweaking maintenance_work_mem?
Regards,
Jayadevan
Hi,
On Thu, Dec 26, 2019 at 7:06 PM stan wrote:
>
>
> _bom_name_key = ( SELECT
> project_bom_key
>FROM inserted )
> ;
>
Try rewriting
_bom_name_key = ( SELECT
project_bom_key
FROM inserted )
asSEL
>
>
> I would conclude that pg-basebackup is placing its output in stderr
> instead of stdout then...
>
>
>
Thanks. Modifying the last potion to '>>$logfile 2>&1' worked.
Regards,
Jayadevan
Hello all,
I have a PostgreSQL backup script which executes daily. The backup creates
no output on "some" days - no pattern observed yet. There is no space
issue.
Here are the relevant lines from the shell script.
mkdir $bdir
echo "Backup began at " `date` | tee -a $logfile
pg_basebackup --chec
18 matches
Mail list logo
