I'm attempting to install pgadmin4 4.27-1.f33 using the pgdg-common
repository on Fedora 33.
I get the following error message
Error:
Problem: conflicting requests
- nothing provides pgadmin4-python3-flask-compress >= 1.4.0 needed by
pgadmin4-4.27-1.f33.x86_64
Any suggestions?
Thanks,
Cliffor
On Tue, May 5, 2020 at 8:37 AM Adrian Klaver
wrote:
> So to be clear you did:
>
> dnf update pgdg-fedora-repo
>
> Have you manually edited the repo file?
>
>
> Adrian,
Thanks - I did actually do the update, but nothing changed. What I noticed
when looking at the /etc/yum.repo folder, there was a
Laurenz Albe (laurenz.a...@cybertec.at), pgsql-gene...@postgresql.org
Draft saved
Make sure this is someone you trust. laurenz.a...@cybertec.at does not
belong to your organization and is not in your contacts.
On Tue, May 5, 2020 at 1:23 AM Laurenz Albe
wrote:
>
> There has been a change in the
When I try to install PostGIS version 2.5 to a Postgresql-11 installation
on Fedora 32 I get warning that nothing provides for these packages:
- nothing provides libproj.so.19()(64bit) needed by
postgis25_11-2.5.4-1.f32.x86_64
- nothing provides libSFCGAL.so.1()(64bit) needed by
postgis25_11-2.5
n 02/07/18 01:43, Clifford Snow wrote:
> > David,
> > Thanks for the suggestion. That really simplifies creating the RANGE.
> >
> > For all, I'm pretty much a postgresql novice, but I've tried to document
> > what I've learned in the hopes that it can h
now.us/articles/Partitioning-Postgresql/
Clifford
On Sun, Jul 1, 2018 at 2:23 PM David Rowley
wrote:
> On 1 July 2018 at 10:15, Clifford Snow wrote:
> > I also leaned that my range partition value I used on a timestamp needed
> to
> > have fractional seconds. I used a range of 2017-01
On Sat, Jun 23, 2018 at 6:42 PM Ravi Krishna wrote:
> Does this help:
> http://ashutoshpg.blogspot.com/2018/06/upgrade-your-partitioning-from.html
>
> Ravi,
Thanks. I used Ashutosh Bapa's blop post as a guideline.
For others attempting this, I first created my parent and child structure.
Then in
I have a large table that needs converting to the native partitioning
available in PG10. I'm looking for a strategy to safely move the data. I
was considering a CREATE TABLE new LIKE old PARTITION ON(my_timestamp).
But I figured postgres would execute that before I could create the child
tables. D
