access old, archived focal packages. I guess this isn't
> wanted behavior?
>
> In case I should direct this problem report to some different place I'd
> be glad if you would tell me.
>
The dist name should be "focal-pgdg-archive" not "focal-pgdg".
--
On Fri, May 3, 2024 at 11:08 PM Adrian Klaver
wrote:
> On 5/3/24 14:06, Magnus Hagander wrote:
> >
> >
> > On Fri, May 3, 2024 at 10:58 PM David Gauthier > <mailto:dfgpostg...@gmail.com>> wrote:
> >
> > psql (15.3, server 14.5) on linux
> >
dIds".
>
Looks like you might need a \d "some_idIds" (include the quotes) since it
has an uppercase characters?
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
ail.com
-- basically that there's some path when we're in ClientWrite that it
doesn't check for interrupts properly. I've unfortunately not had time to
dig into that one anymore.
What version of PostgreSQL and what platform are you on?
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
e release notes for the intermediate versions
as well when looking for changes, as those will not be included in the
notes for the newer version.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
On Fri, May 5, 2023 at 9:23 AM Luca Ferrari wrote:
>
> Hi all,
> this may be tribial, but I'm seeing connections from ::1 in
> pg_stat_activity, and I've never realiuzed that psql converts
> "localhost" in IPv6.
> Is there a way to "force" the hostname localhost to appear as IPv4 or
> am I missing
apset/libpython2.7-64.stp
> [ec2-user@ip-172-31-51-199 ~]$
>
>
> What am I missing? Why won't the postgresql15-contrib install find my
> python shared lib? Does it have to be python3.6 only? Is 3.7, 3.8 no good?
>
>
>
This is not actually answering your question, but you shou
n make them work with how PostgreSQL is
designed.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
x parameter.
To install, you use the "install.bat " command -- where you specify
the directory on the commandline. That's the equivalent of the combination
of --prefix and "make install" on Unix/Linux.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
a useful feature to have, but it's not something that
we have today or that I'm aware of being on anybodys radar. So most
likely, for now you're stuck with either what you're doing today, or
as Laurenz suggests handle it completely in the application. You can't
do the mix.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
ow i can approach to do my Postgresql professional
> certification.
>
>
Hello!
There is no official PostgreSQL certification.
Some PostgreSQL related companies may have their own, but there is no
standard one.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/&
han
>> wherever you installed your postgres from, and therefor it's using those
>> libraries. Perhaps backrest is using the actual default operating system
>> install, and your postgres is a non-standard one?
>>
>> //Magnus
>>
>>
>>>
>>
u installed backrest from a different source than
wherever you installed your postgres from, and therefor it's using those
libraries. Perhaps backrest is using the actual default operating system
install, and your postgres is a non-standard one?
//Magnus
>
> On Tue, Jan 31, 2023 at 7:32 PM Ma
n
you're on, which you didn't specify)
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
they are
issued/confirmed when they are synchronous. Thus terms like WAL = Write
*Ahead* Log.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
On Sun, Jan 15, 2023 at 10:57 PM HECTOR INGERTO
wrote:
>
>
> > But you cannot and should not rely on snapshots alone
>
>
>
> That’s only for non atomic (multiple pools) snapshots. Isn’t?
>
Right. For single-filesystem installs it should be fine. Just make sure it
has both the data and the WAL di
f risk
> taken when snapshotting a PGSQL instance spread across two (or more)
> different pools?
>
>
>
"Don't do it".
If you can't get atomic snapshots, don't do it, period.
You can use them together with a regular online backup. That is
pg_start_backup(
On Mon, Jun 27, 2022 at 12:01 PM Laurenz Albe
wrote:
> On Mon, 2022-06-27 at 11:38 +0200, Magnus Hagander wrote:
> > On Mon, Jun 27, 2022 at 11:30 AM Florents Tselai <
> florents.tse...@gmail.com> wrote:
> > > A few months back (October) I had upgraded a Postgre
ity?
>
>
Are these two really running on the same operating system?
This looks a lot like the locale changes included in newer versions of
glibc, and is in that case dependent on an upgrade of the operating system,
not an upgrade of PostgreSQL. See
https://wiki.postgresql.org/wiki/Locale_data_changes for details.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
ified that the new one works. This looks
like a debian/ubuntu system, which means you probably forgot to run
"pg_dropcluster 12 main"? Or if it's not a debian cluster, the equivalent
of that which results in removing the data directory for 12 along with any
configuration files
and it worked
fine from all of them, even when artificially slowing it down to something
much slower.
So yes, there is *something*, but it's not with in the pg.org
infrastructure.
One thing we got to work that time, I think, was to run:
git config --global http.version HTTP/1.1
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
On Fri, Apr 8, 2022 at 3:27 PM Magnus Hagander wrote:
>
>
> On Fri, Apr 8, 2022 at 3:23 PM Perry Smith wrote:
>
>>
>>
>> On Apr 8, 2022, at 07:47, Jan Wieck wrote:
>>
>> On 4/8/22 01:57, Nikolay Samokhvalov wrote:
>>
>> On Thu, Apr 7, 2022
ill
fail to commit if the foreign key is broken *at that point*. But it lets
you do things like modify multiple tables that refer to each other, and
have the changes only checked when they're all done.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
On Fri, Apr 8, 2022 at 3:07 PM Jan Wieck wrote:
> On 4/8/22 08:58, Magnus Hagander wrote:
> > A side-note on this, which of course won't help the OP at this point,
> > but if the general best practice of not running the application with a
> > highly privileged accoun
a standby server, and there is replication lag
>
There's also:
c) The SELECT runs in a transaction stat *started* before the transaction
that a runs in. (Assuming it then retries with a new transaction later,
that is)
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
user permissions, none of which it's
recommended that the application run with. Doesn't help once the problem
has occurred of course, but can help avoid it happening in the future.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
new database from initdb (I would also say create a
completely new filesystem underneath it since that's where the corruption
is, if that's easily done)
4. Restore the pg_dump. At this point it will throw errors on any foreign
keys that are "off", and you will have to c
On Fri, Apr 1, 2022 at 5:08 PM Daniele Varrazzo
wrote:
> On Fri, 1 Apr 2022 at 17:00, Magnus Hagander wrote:
> >
> > On Fri, Apr 1, 2022 at 4:52 PM Daniele Varrazzo <
> daniele.varra...@gmail.com> wrote:
> >>
> >> On Fri, 1 Apr 2022 at 16:28, Magnus H
On Fri, Apr 1, 2022 at 4:52 PM Daniele Varrazzo
wrote:
> On Fri, 1 Apr 2022 at 16:28, Magnus Hagander wrote:
>
> > Stretch also goes end of life on June 30 2022, so just a few months
> away. You definitely shouldn't be using that.
>
> The platform is part of the Py
hs away.
You definitely shouldn't be using that.
Buster is also considered the "oldstable" version. You should probably be
using bullseye. (I assume you're talking about some generic binaries and
not the DEB packages of course -- DEB packages should be built on their
corres
obviously I understand creating many indexes will impact write
> performance and space will be utilized.
>
> Would like to know if creating indexes in this manner can create any other
> issues or inputs on the whole topic of indexes in JSONB types.
>
You should not be creating i
have worked "by chance".
The llvm dependency comes from the JIT functionality, which was added
in PostgreSQL 11, so it not being a dependency in an older version
than that makes perfect sense.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
o I tried to build
> llvm-toolset-clang from scratch, but that doesn't solve the problem.
Note that the PGDG repositories are not supported on Amazon Linux.
https://www.postgresql.org/download/linux/redhat/ has a list of
supported platforms for them.
On CentOS, which is, you need to r
t's using a system-default version of libpq.so which
is from an older version.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
ian packaging team packages both the packages for debian and those for
apt.postgresql.org, so it's still the same people that does.
So there's actually a lot more crossover there than when you look at the
EDB provided packages for example, where the team is completely
indepdendent.
--
cases when
> looking at the compression type of the vacuumed table attributes:
>
Oh dang, I missed that this was reverted. Thanks for pointing that out!
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
e db.
>
> Is there a smarter way to do this ?
>
>
It should be enough to VACUUM FULL the table. (but it has to be VACUUM
FULL, not a regular vacuum). Or CLUSTER.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
uilt
> that way: each row INSERTed means a round trip between PostgreSQL and Oracle.
>
Just as a note, with PostgreSQL 14 the FDW APIs allow batch insert. It
should be possible to update oracle_fdw to take advantage of that as
well, right?
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
link you get to
https://github.com/docker-library/postgres which clearly explains what
"type of official" it is.
That said, as long as you use the debian based version of their
container, it should be trivial to add any extension that's supported
on Debian, which definitely inclu
by *postgresql*. (And of
course, AWS or Azure or whomever do whatever they want, but I assume
they're including pg_partman because it's a very popular extension)
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
eploy with cron.
And FWIW, in reference to the discussions about AWS, it is supported on RDS.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
nd add it
to https://www.postgresql.org/about/licence/ -- similar to how we
explain that we're not going to change license... Like a "what does
this mean" section or something..
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
On Thu, Aug 12, 2021 at 4:38 PM hubert depesz lubaczewski
wrote:
>
> On Thu, Aug 12, 2021 at 11:32:15AM +0200, Magnus Hagander wrote:
> > Which database are you connected to? If you just want to look at the
> > global stats, it might help to be connected to a database that is
second. Second call in the same connection, different txn,
> 0.8s.
>
> Second call in the same transaction as first - 0.053ms.
>
> So it definitely suggests that loading the stats file is the problem.
Yes, definitely.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
> insert into bar(f,b) values(foo,bar) returning * into v_row;
> return v_row;
> END;
> $$ language plpgsql;
You can write that either as:
RETURN NEXT v_row;
(the NEXT being the missing keyword)
Or just the whole thing as
RETURN QUERY INSERT INTO ... RETURNING *
and get
thing goes wrong, but just keep an extra
standby node around to fail over to if everything blows up and you
have that covered.
The fact that pg_upgrade *doesn't* take ages to deal with medium size
databases and up is the main reason it *exists*.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
ent third party.
The official PostgreSQL archives are on https://www.postgresql.org/list/
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
s like this to
webmas...@postgresql.org, so they don't have to go out to thousands of
people. They'll still be picked up of course, but that will be more
targeted.)
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
gathering those data and which database is responsible for this?
Yes. This is new in PostgreSQL 12
(https://www.postgresql.org/docs/12/release-12.html). It tracks
accesses to shared objects
(https://www.postgresql.org/docs/12/monitoring-stats.html#PG-STAT-DATABASE-VIEW).
--
Magnus Hagander
Me:
gain. It has
explicitly attached the fiel to the HTML part, which means that
anybody viewing the plaintext part (such as the PostgreSQL archives..)
will not see it.
I have no idea how to make it not do that, but AFAIK it's only Apple
Mail that's shown this problem.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
tallations using it today are unsafe, it is recommended that
you don't use it even before then. It basically exists for backwards
compatibility with PostgreSQL prior to 9.6.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
27;t believe there are any plans to change this in PostgreSQL, as
it's generally not a problem.
AWS Aurora however, is not PostgreSQL, it's a different database
(which shares some parts, but it's fundamentally quite different) It's
also not open source so there is no way for us to
_dump.
>
> > Anyone seen similar issue?
>
> Nope, something very odd going on here.
Do you by any chance have more than one version of PostgreSQL running
at the same time for different clusters? It kind of sounds like it's
picking up the wrong version at some point.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
g version of the docs (now on
https://www.postgresql.org/docs/devel/install-binaries.html) will make
it more clear that we also recommend using packages on for example
Linux as well, when they are available. So the recommendation is
generic, not Windows-specific.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
> (1 row)
Yeah, you want to use pg_relation_filenode(oid) rather than looking
directly at relfilenode.
When compared to the filesystem, it's probably even easier to use
pg_relation_filepath(oid).
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
erabilities between 11.2 and 11.11, as you can
see on https://www.postgresql.org/support/security/11/. So it sounds
like your vulnerability scanner is right and that you need to install
the updates.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
is download is
provided externally by EDB" (very much open to input on exactly what
the sentence should be)? Or were you guys thinking in the line that we
should have one of those "you are now leaving postgresql.org"-steps in
between with a second click?
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
de
mode".
There's been some recent work on trying to find a remedy for this, but
nothing is available at this point. You'll need to either trim the
number of objects if you can (by maybe manually dumping them out to
files before the restore and then reloading them back in later), or
just add more memory/swap to the machine.
Long term you should probably consider switching to using bytea
columns when you have that many objects.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
dy from the mailing list admins help me out here?
Hi!
You seem to have hit a bug in our oauth1 processing (twitter is the
only provider we use oauth1 for, the others use oauth2). I believe
it's been fixed now, please try again.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
ing about it).
Buttom line is that while it may be a good tool for reading, it is
*not* a good tool for posting, at least not until they fix their basic
handling of email.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
ges
Note that this is triggered by the Ubuntu upgrade, not by upgrading
PostgreSQL -- that's why it happend even when you keep using the same
PostgreSQL version.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
hing, and
then reply to that through your normal email. It's not the most
convenient workflow, but if you mostly read and only very seldom post,
it works.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
cluded your problem seems to be with the
proprietary server product from EnterpriseDB, not with PostgreSQL.
For support with that, you should contact the EDB support channels.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
On Thu, Jan 7, 2021 at 10:40 AM Paul Förster wrote:
>
> Hi Magnus,
>
> > On 06. Jan, 2021, at 16:57, Magnus Hagander wrote:
> >
> > Yes. But you have a really hacky environment :P
>
> actually not. We have an old LDAP which we want to retire this year. And
ntence -- without that one, your
reading of it would make more sense. See also the following parameter,
ldaptls, which uses similar language.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
On Wed, Jan 6, 2021 at 4:39 PM Paul Förster wrote:
>
> Hi Magnus,
>
> > On 06. Jan, 2021, at 15:48, Magnus Hagander wrote:
> >
> > Only if you can create rules in your pg_hba.conf file that knows where
> > the users are. You can specify multiple servers on one
bonus you get Kerberos which is a lot more
secure than ldap for auth.. It might have a slightly higher barrier
of entry, but could probably pay off well in a case like this.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
sql.org/
If not, then you will have to build from source manually -- the old
versions of PostgreSQL are still available in source form on
https://ftp.postgresql.org/pub/source/
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
n.nnn.n.nnn", user
> "kalle", database "postgres", SSL off
> FATAL: no pg_hba.conf entry for host "nn.nnn.n.nnn", user "kalle", database
> "postgres", SSL off
>
> KR Mikael Gustavsson, SMHI
>
>
> ___
1.3
when you use the old version...
I assume you're running both the 11 and the 13 client on the same host?
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
specifically looking at the Debian or Ubuntu packages, you can
find the full packaging information in the salsa repositories at
https://salsa.debian.org/postgresql/postgresql. It will have all teh
details you need.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/&g
mand really not have a %f in it anywhere? That
definitely seems wrong... But it does seem to copy some files correct,
which would be weird if it doesn't. Mistake in the report, or is there
something really weird going on with that PostgreSQL_DEV not being a
directory but instead some "magic file"?
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
mostly
fine on RHEL7. But if you don't actually show us what your dependency
problems are, we can't tell you how to fix it...
(And why not use Patroni from the PDGD repositories?)
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
endent objects too.
If you have no functions using it, it will just go away, and once you
have dropped it in both databases you should be good to go.
And of course, if there are functions depending on it, you should
rebuild those on plpython3u before you drop plpython2u (or drop the
functions if they're not in use).
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
On Fri, Nov 13, 2020 at 7:10 PM Magnus Hagander wrote:
> dnf install --excludepkg proj --excludepkg proj-datumgrid postgis30_12
> postgis30_12-devel postgis30_12-utils postgis30_12-client postgis30_12-docs
>
> On Fri, Nov 13, 2020 at 7:01 PM Tom Lane wrote:
> >
> &g
:
dnf install --excludepkg proj --excludepkg proj-datumgrid postgis30_12
as a workaround.
*If* the root cause is the same one, that is...
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
ple this thread here
https://www.postgresql.org/message-id/flat/61463e206b7c4c0ca17b03a59e890b78%40lmco.com,
and the config on https://github.com/rc9000/postgres-fail2ban-lockout.
(probably needs some small adaptations, but as a base it should work).
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
it, like
SELECT "cast" FROM test
(and the same when you create the table, or indeed any references to the column)
zone is not, and should be fine.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
ore muscles": "No",
> "Have you travelled outside of Canada in the past 14 days?": "No",
> "Have you had close contact with a confirmed or probable case of
> COVID-19?": "No"
> }
>
> If the order had remained the same, it's child's play to pull the data out
> and present it in a report, even if the data elements change.
> But... seen above, the order gets mixed up.
>
> Any ideas?
The json standard declares that the keys in a document are unordered,
and can appear at any order.
In PostgreSQL, jsonb will not preserve key ordering, as a feature for
efficiency. The plain json datatype will, so if key ordering is
important you should use json instead of jsonb (but you should
probably also not use the json format in general, as it does not
guarantee this)
See https://www.postgresql.org/docs/13/datatype-json.html
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
m before handing the actual call up to the operating system. It's
completely independent of how the file is opened.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
at
https://www.postgresql.org/docs/13/server-start.html talks about this
behaviour, but only notes that crash recovery might be a reason to hit
this timeout. Maybe it needs to also mention replication (and probably
archive recovery)?
> The best place to discuss this would be the "pgsql-pkg-yum" list.
I don't think this is a packaging issue, all the RPMs did was enable
the functionality that's in core postgresql.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
onsibility over to your Kerberos system. Then you can set that one
up to require you to manually type in a password or equivalent to get t a
ticket, and configure expiry on that ticket.
//Magnus
*发件人:* Magnus Hagander [mailto:mag...@hagander.net]
>
> *发送时间:* 2020年10月27日 17:00
> *收件
course have to figure out how to securely authenticate the postgres
OS user on the standby node to the Kerberos system, but that's doable.
(Though I believe most Kerberos implementations also rely on filesystem
security to protect the tickets, so if you don't trust your filesystem, you
may have a problem with that -- as well as indeed most other authentication
systems -- so you'd have to investigate that within the kerberos system).
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
hasn't made
> production yet.
>
PostgreSQL does not have such a thing as "open feature requests".
You can find patches that are currently being worked on at
https://commitfest.postgresql.org/, or on discussions in the list archives.
--
Magnus Hagander
Me: https://www.
Yes, it is free.
> PostgreSQL(9.4 - 11) support subscription
>
The PostgreSQL community does not provide subscriptions. You can find
information about the support options, both free and paid, at
https://www.postgresql.org/support/.
--
Magnus Hagander
Me: https://www.hagande
On Wed, Oct 14, 2020 at 5:23 PM Tom Lane wrote:
> Magnus Hagander writes:
> > On Wed, Oct 14, 2020 at 5:10 PM Tom Lane wrote:
> >> It's fairly annoying that this doesn't work:
> >> regression=# select pg_size_bytes(setting||' '||unit) fro
On Wed, Oct 14, 2020 at 5:10 PM Tom Lane wrote:
> Magnus Hagander writes:
> > On Wed, Oct 14, 2020 at 3:57 PM Thomas Kellerer wrote:
> >> select pg_size_bytes(setting) * 8192
> >> from pg_settings
> >> where name = 'shared_buffers';
>
>
shared_buffers';
>
> Ah, forgot that shared_buffers is in 8K pages.
>
> So you actually need:
>
>select pg_size_bytes(setting) * 8192
>from pg_settings
>where name = 'shared_buffers';
>
Actually, it doesn't have to be in 8k pages, that d
> Was it?
>
> Pre-10 it was:
>
> MAJOR.MAJOR.PATCH
>
Yeah the fact that it kind of looked like semver, but *wasn't* semver, is
probably one of the (many) things that confused people. It definitely
wasn't semver.
--
Magnus Hagander
Me: https://www.hagande
adhineni
wrote:
> I could see block read I/O errors in /var/log/syslog. if those error fixed
> by OS team, will it require recovery.
>
> Also can i use LIMIT and OFFSET to locate corrupted rows?
>
> Thanks in advance
>
> Regards,
> Vasu Madhineni
>
> On Wed, Sep
urn
rows in a consistent/predictable order. So as long as that query is part of
what you're doing, you should not be surprised if you get the rows in an
inconsistent/unpredictable order, with whatever follow-on effects that
might have. (And it can lead to weird follow-on effects like the ones
y
s the same.
Once it fails, you've found a corrupt block...
//Magnus
On Tue, Sep 15, 2020 at 12:46 PM Vasu Madhineni
wrote:
> Is it possible to identify which rows are corrupted in particular tables.
>
> On Tue, Sep 15, 2020 at 5:36 PM Magnus Hagander
> wrote:
>
>>
&g
ve caused corruption elsewhere as well, so
whatever verification you can do against other tables, you should do as
well.
You'll of course also want to check any kernel logs or storage system logs
to see if they can give you a hint as to what happened, but they are
unlikely to ac
and all should be taken care of.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
On Tue, Sep 8, 2020 at 5:16 PM Tom Lane wrote:
> Magnus Hagander writes:
> > On Tue, Sep 8, 2020 at 4:38 PM Tom Lane wrote:
> >> The reason that's not so is that whether or not transaction A *has*
> >> touched table B is irrelevant. It *could* read tab
On Tue, Sep 8, 2020 at 4:38 PM Tom Lane wrote:
> Magnus Hagander writes:
> > Oh sure, but there is clearly *something* going on, so we should try to
> > figure that out. Because a transaction running multiple independent
> selects
> > with the defaults settings
On Tue, Sep 8, 2020 at 4:01 PM Michael Holzman
wrote:
>
>
> On Tue, Sep 8, 2020 at 4:25 PM Magnus Hagander wrote:
>
>>
>>
>> Whether you have autocommit on or off, you can *always* control things
>> explicitly. And you can certainly run "multi-statemen
(Please don't drop the mailinglist from CC, as others are likely interested
in the responses)
On Tue, Sep 8, 2020 at 3:06 PM Michael Holzman
wrote:
>
>
> On Tue, Sep 8, 2020 at 3:03 PM Magnus Hagander wrote:
>
>> A PostgreSQL SELECT does *not* open a transaction past the
On Thu, Sep 3, 2020 at 12:43 PM Hou, Zhijie
wrote:
> Hi all
>
> In master branch, I found a typo in Comments of function
> HandleProcSignalBarrierInterrupt.
> See the attachment for the patch.
>
>
Thanks, pushed.
//Magnus
, varchar just takes a number, not the special construct with
BYTE. PostgreSQL varchar:s always limit the size based on number of
characters, not bytes.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
1 - 100 of 181 matches
Mail list logo
