## Jeremy Schneider (schnei...@ardentperf.com):
> I'm running Postgres in containers, and recently did some analysis of
> the total container sizes. I posted some analysis over on the debian
> packaging mailing list [1] [2]. The TLDR is that LLVM alone makes up
> 33% of a postgres container's byte
## Heikki Linnakangas (hlinn...@iki.fi):
> This is a bit weird state. What exactly is "upgrading"? I guess you
> mean pg_upgrade, but lots of people use pg_dump & restore or logical
> replication or something else entirely for upgrading. That's
> indistinguishable from setting a pre-hashed MD5 pas
## Fabrice Chapuis (fabrice636...@gmail.com):
> From a conceptual point of view I think that specific wals per subscription
> should be used and stored in the pg_replslot folder in order to avoid
> working directly on the wals of the instance.
> What do you think about this proposal?
I think that
Hi,
## Fabrice Chapuis (fabrice636...@gmail.com):
> on the other hand there are 2 slots for logical replication which display
> status extended. I don't understand why given that the confirmed_flush_lsn
> field that is up to date. The restart_lsn remains frozen, for what reason?
There you have i
## Fabrice Chapuis (fabrice636...@gmail.com):
> We have a cluster of 2 members (1 primary and 1 standby) with Postgres
> version 14.9 and 2 barman server, slots are only configured for barman,
> barman is version 3.7.
The obvious question here is: can both of those barmans keep up with
your datab
## tender wang (tndrw...@gmail.com):
> But I want to know why we don't prune when just have latter partition key
> in whereClause.
Start with the high level documentation
https://www.postgresql.org/docs/current/sql-createtable.html#SQL-CREATETABLE-PARTITION
where the 5th paragraph points you to
h
## GF (phab...@gmail.com):
> In the past I needed such a pg_servername() function because in a project I
> was engaged on they needed to distribute "requests" directed to a in-house
> management service running on network servers, and each one had a DB, so we
> went with pglogical to be used as a
Hi,
## Laetitia Avrot (laetitia.av...@gmail.com):
> I understand your point and sure enough, my customer could set and use the
> cluster_name for that purpose. I totally disagree with using
> inet_server_addr() for that purpose as there are so many different network
> settings with VIPs and so on
## Laetitia Avrot (laetitia.av...@gmail.com):
> For my customer, their use case is to be able from an SQL client to double
> check they're on the right host before doing things that could become a
> production disaster.
Why not use cluster_name for that? Even if it may not be relevant
for their
## Dimos Stamatakis (dimos.stamata...@servicenow.com):
> In our scenario we changed the permissions of this function in PG14.5
> (via an automated tool) and then pg_upgrade tries to change the
> permissions in PG15.1 as well.
Given that this function wasn't even documented and did nothing but
thr
## Peter Eisentraut (peter.eisentr...@enterprisedb.com):
> First of all, is this a standard installation of this OS, or is perhaps
> something incomplete, broken, or unusual about the current OS installation?
Alpine uses musl libc, on which you need package musl-locales to get
a /usr/bin/locale.
## Zhihong Yu (z...@yugabyte.com):
> I was able to create gin index on inet column in PG.
>
> GIN is good with points/elements in sets. Is gin a good index for inet
> column ?
> It seems gist index would be better.
Why not use btree? The common operations are quite supported with that.
(Common o
## Tom Lane (t...@sss.pgh.pa.us):
> Isn't that a flat out violation of POSIX 8.3 Other Environment Variables?
>
> HOME
> The system shall initialize this variable at the time of login to
> be a pathname of the user's home directory. See .
>
> To claim it's not, you have to cl
## Tom Lane (t...@sss.pgh.pa.us):
> Given the POSIX requirements, it's basically impossible to believe
> that there are interesting cases where $HOME isn't set.
When I look at a random Debian with the usual PGDG packages, the
postmaster process (and every backend) has a rather minimal environment
## Pavel Stehule (pavel.steh...@gmail.com):
> it is not consistent with other \g* commands. Maybe a new statement \senv
> ? But what is the use case? You can just press ^z and inside shell write
> echo $xxx, and then fg
That does not work: backgrounding psql will put you into your original
shell
## Esteban Zimanyi (ezima...@ulb.ac.be):
> Is there a step-by-step procedure specified somewhere?
The first step is not to disable autovacuum... (why would you want to
do that?).
> For example, before launching the tests there is a load.sql file that loads
> all the test tables. The file starts
## Esteban Zimanyi (ezima...@ulb.ac.be):
> I have tried
> alter system set autovacuum = off;
> but it does not seem to work.
Did you reload the configuration ("SELECT pg_reload_conf()" etc) after
that? If not, that's your problem right there.
Regards,
Christoph
--
Spare Space
## Magnus Hagander (mag...@hagander.net):
> Ugh, yeah, please don't do that. Renaming them just to make it "look more
> modern" helps nobody, really. Especially if the suggestion is people should
> be using the shared-launcher binary anyway.
Quick, let's invent a fancy name like "microcommand" fo
## Robert Willis (rwil...@abinitio.com):
> How do I go about this?Is there a specific-mailing list (other than
> this one) for that purpose?
https://odbc.postgresql.org/
"psqlODBC is developed and supported through the pgsql-o...@postgresql.org
mailing list."
Regards,
Christoph
--
Spare S
## Sergiu Velescu (sergiu.vele...@endava.com):
> OnLogin/Logout.
> I want to log/audit each attempt to login (successful and/or not).
log_connections/log_disconnections
> Who/how long was logged in DB (who logged in out of business hours
> (maybe deny access)).
Use PAM authentication.
> Set se
## Stephen Frost (sfr...@snowman.net):
> We already have a reserved namespace when it comes to roles,
> specifically "pg_".. why invent something new like this '&' prefix when
> we could just declare that 'pg_superusers' is a role to which all
> superusers are members? Or something along those l
## Tomas Zubiri (m...@tomaszubiri.com):
> We already established that a tcp connection was subpar in terms of
> latency, we shall note then that a tcp connection is subpar in terms
> of security.
It's an entirely different thing, I'd argue. I'm not even convinced
that an error message is a bad th
## Tomas Zubiri (m...@tomaszubiri.com):
> The problem was that running the command psql without arguments
There's an excellent manpage for psql, which can also be found online:
https://www.postgresql.org/docs/current/app-psql.html
In there you'll find a section "Connecting to a Database", with t
## Michael Paquier (mich...@paquier.xyz):
> Total bytes and free bytes looks like a good first cut. Have you
> looked at the portability of statfs() on other BSD flavors and
> Solaris?
"The statfs() system call first appeared in 4.4BSD." (from the statfs(2)
manpage on FreeBSD). struct statfs dif
## Tom Lane (t...@sss.pgh.pa.us):
> I took a stab at fixing this, but lacking a Windows environment
> to test in, I can't be sure if it works. The attached does kinda
> sorta work if I run it in a Linux environment --- but I found that
> system() doesn't automatically expand "t/*.pl" on Linux. I
## Magnus Hagander (mag...@hagander.net):
> You'd solve more
> of that by having the middle layer speak "raw device" underneath and be
> able to sit on top of things like iSCSI (yes, really).
Back in ye olden days we called these middle layers "kernel" and
"filesystem" and had that maintained by
## Surafel Temesgen (surafel3...@gmail.com):
> Currently we can not moves data from a file to a table based on some
> condition on a certain column
You can:
COPY ( query ) TO 'filename';
There's even an example in the documentation:
https://www.postgresql.org/docs/10/static/sql-copy.html
"To c
## Michael Paquier (mich...@paquier.xyz):
> Thanks Iwata-san. I was just trying to apply the patch but it failed so
> the new status is fine. On top of taking care of the rebase, please
> make sure of the following:
OK, that was an easy one.
> - Calling pg_ls_dir_files() with missing_ok set to
Hi,
## Iwata, Aya (iwata@jp.fujitsu.com):
> I think it is convenient to be able to check the archive_status
> directory contents information.
>
> I reviewed patch. It applies and passes regression test.
Great, thanks!
> All similar function are named pg_ls_***dir. It is clear these functio
## Michael Paquier (mich...@paquier.xyz):
> Okay, could you add this patch to the next commit fest? Here it is:
> https://commitfest.postgresql.org/20/
And here's the patch: https://commitfest.postgresql.org/20/1813/
Regards,
Christoph
--
Spare Space
Hi,
while setting up monitoring for a new PostgreSQL instance, I noticed that
there's no build-in way for a pg_monitor role to check the contents of
the archive_status directory. We got pg_ls_waldir() in 10, but that
only lists pg_wal - not it's subdirectory. It seems listing the
archive_status di
## ramsiddu007 (ramsiddu...@gmail.com):
> If i remove first character it's run. That first
> character is invisible, I have checked that *ascii* value, it is *65279*.
That's not an ASCII-value, ASCII has 8 bits at most.
What you've got there is a UTF-16 Byte Order Mark: 65279 is 0xfeff
(one of t
## Tatsuo Ishii (is...@sraoss.co.jp):
> Currently pg_rewind copies all files including postgresql.conf. It
> would be nice if pg_rewind has an option to not copy
> postgresql.conf.
How about including a file outside the data directory with "local"
settings? Like "include /some/where/else/local.co
33 matches
Mail list logo
