Rolling forward to 10.1, new issue...

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Rolling forward to 10.1, new issue...

Karl Denninger

I'm starting to roll forward to 10.1 in a couple of places and have run into a very odd problem -- the "pgcrypto" functions disappeared.

I've got the contrib module loaded but the functions are not there.  For example:

pgsql=# select crypt('test', gen_salt('md5'));
ERROR:  function gen_salt(unknown) does not exist
LINE 1: select crypt('test', gen_salt('md5'));
                             ^
HINT:  No function matches the given name and argument types. You might need to add explicit type casts.

I shut down the server in question, went back and re-made the pgcrypto contrib directory (it HAD been installed previously) and re-did the install, then restarted the server -- no change.  I've never seen this problem before....

Not quite sure where to look next..... any ideas?

--
Karl Denninger
[hidden email]
The Market Ticker
[S/MIME encrypted email preferred]

smime.p7s (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Rolling forward to 10.1, new issue...

Tom Lane-2
Karl Denninger <[hidden email]> writes:
> I'm starting to roll forward to 10.1 in a couple of places and have run
> into a very odd problem -- the "pgcrypto" functions disappeared.

Maybe you forgot "CREATE EXTENSION"?

                        regards, tom lane

Reply | Threaded
Open this post in threaded view
|

Re: Rolling forward to 10.1, new issue...

Karl Denninger

On 1/11/2018 11:48, Tom Lane wrote:

Karl Denninger [hidden email] writes:
I'm starting to roll forward to 10.1 in a couple of places and have run
into a very odd problem -- the "pgcrypto" functions disappeared.
Maybe you forgot "CREATE EXTENSION"?

			regards, tom lane
Hmmm.... this was an upgrade from 9.6 and it *was* working there -- it's not a new install.  Wouldn't that persist across the upgrade and, when the "gmake install" was done on the contrib module wouldn't it be picked up?

I'll check that... it makes sense but I would have expected the roll-forward to work seamlessly (I used pg_upgrade, not a dump/restore.)

--
Karl Denninger
[hidden email]
The Market Ticker
[S/MIME encrypted email preferred]

smime.p7s (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: Rolling forward to 10.1, new issue...

Karen Stone-2
In reply to this post by Tom Lane-2
Can you please remove me from this list.  Thanks!

Karen Stone| Technical Services| Eldorado |a Division of MphasiS
5353 North 16th Street, Suite 400, Phoenix, Arizona 85016-3228
Tel (928) 892 5735 | www.eldoinc.com | www.mphasis.com |[hidden email]


-----Original Message-----
From: Tom Lane [mailto:[hidden email]]
Sent: Thursday, January 11, 2018 10:49 AM
To: Karl Denninger <[hidden email]>
Cc: [hidden email]
Subject: Re: Rolling forward to 10.1, new issue...

Karl Denninger <[hidden email]> writes:
> I'm starting to roll forward to 10.1 in a couple of places and have
> run into a very odd problem -- the "pgcrypto" functions disappeared.

Maybe you forgot "CREATE EXTENSION"?

                        regards, tom lane


Reply | Threaded
Open this post in threaded view
|

Re: Rolling forward to 10.1, new issue...

Keith
In reply to this post by Karl Denninger


On Thu, Jan 11, 2018 at 1:16 PM, Karl Denninger <[hidden email]> wrote:

On 1/11/2018 11:48, Tom Lane wrote:

Karl Denninger [hidden email] writes:
I'm starting to roll forward to 10.1 in a couple of places and have run
into a very odd problem -- the "pgcrypto" functions disappeared.
Maybe you forgot "CREATE EXTENSION"?

			regards, tom lane
Hmmm.... this was an upgrade from 9.6 and it *was* working there -- it's not a new install.  Wouldn't that persist across the upgrade and, when the "gmake install" was done on the contrib module wouldn't it be picked up?

I'll check that... it makes sense but I would have expected the roll-forward to work seamlessly (I used pg_upgrade, not a dump/restore.)

--
Karl Denninger
[hidden email]
The Market Ticker
[S/MIME encrypted email preferred]

That should persist yes. Did you install pgcrypto into a specific schema? Check the search_path of the user that is trying to use pgcrypto.

Keith
Reply | Threaded
Open this post in threaded view
|

Re: Rolling forward to 10.1, new issue...

Karl Denninger
On 1/12/2018 12:46, Keith wrote:


On Thu, Jan 11, 2018 at 1:16 PM, Karl Denninger <[hidden email]> wrote:

On 1/11/2018 11:48, Tom Lane wrote:

Karl Denninger [hidden email] writes:
I'm starting to roll forward to 10.1 in a couple of places and have run
into a very odd problem -- the "pgcrypto" functions disappeared.
Maybe you forgot "CREATE EXTENSION"?

			regards, tom lane
Hmmm.... this was an upgrade from 9.6 and it *was* working there -- it's not a new install.  Wouldn't that persist across the upgrade and, when the "gmake install" was done on the contrib module wouldn't it be picked up?

I'll check that... it makes sense but I would have expected the roll-forward to work seamlessly (I used pg_upgrade, not a dump/restore.)

--
Karl Denninger
[hidden email]
The Market Ticker
[S/MIME encrypted email preferred]

Nope, it was originally installed into template1 and should have been inherited.

Create extension worked but I have no idea why the pg_upgrade didn't carry it forward -- I have used pg_upgrade before before (the installation in question has been around for a long time)  without incident.  The only "gotcha" I've run into with pg_upgrade before was the moving of tsearch2 into the base which led me to have a bit of fun with upgrading to 10.x.

I'll see if I can find a way to reproduce this if I can get the time to spin up a copy of the 9.6 database (this particular installation is not ridiculously large) from backups and run the upgrade again.  I popped in here because it was completely unexpected, given that the database in question had previously been running under v9 and had stored passwords encrypted with the functions in the table.  As soon as it was upgraded verification broke since the extension disappeared.

--
Karl Denninger
[hidden email]
The Market Ticker
[S/MIME encrypted email preferred]

smime.p7s (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Rolling forward to 10.1, new issue...

Keith


On Fri, Jan 12, 2018 at 2:27 PM, Karl Denninger <[hidden email]> wrote:
On 1/12/2018 12:46, Keith wrote:


On Thu, Jan 11, 2018 at 1:16 PM, Karl Denninger <[hidden email]> wrote:

On 1/11/2018 11:48, Tom Lane wrote:

Karl Denninger [hidden email] writes:
I'm starting to roll forward to 10.1 in a couple of places and have run
into a very odd problem -- the "pgcrypto" functions disappeared.
Maybe you forgot "CREATE EXTENSION"?

			regards, tom lane
Hmmm.... this was an upgrade from 9.6 and it *was* working there -- it's not a new install.  Wouldn't that persist across the upgrade and, when the "gmake install" was done on the contrib module wouldn't it be picked up?

I'll check that... it makes sense but I would have expected the roll-forward to work seamlessly (I used pg_upgrade, not a dump/restore.)

--
Karl Denninger
[hidden email]
The Market Ticker
[S/MIME encrypted email preferred]

Nope, it was originally installed into template1 and should have been inherited.


Creating it in template1 does not automatically inherit it to all other databases. That only causes it to be installed in databases created after you installed it to template1.


Create extension worked but I have no idea why the pg_upgrade didn't carry it forward -- I have used pg_upgrade before before (the installation in question has been around for a long time)  without incident.  The only "gotcha" I've run into with pg_upgrade before was the moving of tsearch2 into the base which led me to have a bit of fun with upgrading to 10.x.

I'll see if I can find a way to reproduce this if I can get the time to spin up a copy of the 9.6 database (this particular installation is not ridiculously large) from backups and run the upgrade again.  I popped in here because it was completely unexpected, given that the database in question had previously been running under v9 and had stored passwords encrypted with the functions in the table.  As soon as it was upgraded verification broke since the extension disappeared.

--
Karl Denninger
[hidden email]
The Market Ticker
[S/MIME encrypted email preferred]

Yeah, I think you're going to have to get a repeatable set of steps here. Could very well be a problem, but without that, it's very hard to figure out what went wrong here.

Keith


Previous Thread Next Thread