ERROR: improper qualified name (too many dotted names) when trying ALTER FUNCTIONSyntax error when trying to...

Are encryption algorithms with fixed-point free permutations inherently flawed?

Why do we interpret the accelerated expansion of the universe as the proof for the existence of dark energy?

Can I legally make a website about boycotting a certain company?

How can I portray body horror and still be sensitive to people with disabilities?

What did Putin say about a US deep state in his state-of-the-nation speech; what has he said in the past?

Given the mapping a = 1, b = 2, ... z = 26, and an encoded message, count the number of ways it can be decoded

Can a Hydra make multiple opportunity attacks at once?

Do these large-scale, human power-plant-tending robots from the Matrix movies have a name, in-universe or out?

Do error bars on probabilities have any meaning?

Why is quixotic not Quixotic (a proper adjective)?

Why write a book when there's a movie in my head?

Found a major flaw in paper from home university – to which I would like to return

Buying a "Used" Router

Why does this quiz question say that protons and electrons do not combine to form neutrons?

How to modify 'inter arma enim silent leges' to mean 'in a time of crisis, the law falls silent'?

What does it mean when an external ID field follows a DML Statement?

Does this property characterize the odd primes?

Did the characters in Moving Pictures not know about cameras like Twoflower's?

Was the Soviet N1 really capable of sending 9.6 GB/s of telemetry?

TikZtree with asymmetric siblings

Can I combine Divination spells with Arcane Eye?

What does "don't have a baby" imply or mean in this sentence?

Is there a way to pause a running process on Linux systems and resume later?

When distributing a Linux kernel driver as source code, what's the difference between Proprietary and GPL license?



ERROR: improper qualified name (too many dotted names) when trying ALTER FUNCTION


Syntax error when trying to import database from two PostgreSQL databasesCannot connect to server. Too many symbolic links. Postgres ErrorERROR: text search configuration name “english” must be schema-qualifiedXRC error when trying to access PostgreSQL view properties“parameter name used more than once” error when declaring function - why this is happening?Why does this function return an error by itself, but when called by another function it doesn't return an error?How to quote qualified table name with format() function?Is there a way to connect to postgres when have error “sorry, too many clients already ”?













3















Working with Amazon Aurora Postgres Version 2.0, which is basically PostgreSQL 10.4 with a modified storage layer.



Trying to restore a dump that contains multiple lines like:



ALTER FUNCTION myschema.f_myfunc(anyarray, anyelement) OWNER TO myrole;


I get an error message for every ALTER FUNCTION like that:




ERROR:  improper qualified name (too many dotted names)



Trying the same in psql produces the same error. Even with the simplest form:



ALTER FUNCTION foo() OWNER TO myrole;


There are no dotted names. I found similar complaints here:
https://forums.aws.amazon.com/thread.jspa?messageID=872096&tstart=0



Must be a bug in Aurora - or am I missing something?










share|improve this question





























    3















    Working with Amazon Aurora Postgres Version 2.0, which is basically PostgreSQL 10.4 with a modified storage layer.



    Trying to restore a dump that contains multiple lines like:



    ALTER FUNCTION myschema.f_myfunc(anyarray, anyelement) OWNER TO myrole;


    I get an error message for every ALTER FUNCTION like that:




    ERROR:  improper qualified name (too many dotted names)



    Trying the same in psql produces the same error. Even with the simplest form:



    ALTER FUNCTION foo() OWNER TO myrole;


    There are no dotted names. I found similar complaints here:
    https://forums.aws.amazon.com/thread.jspa?messageID=872096&tstart=0



    Must be a bug in Aurora - or am I missing something?










    share|improve this question



























      3












      3








      3








      Working with Amazon Aurora Postgres Version 2.0, which is basically PostgreSQL 10.4 with a modified storage layer.



      Trying to restore a dump that contains multiple lines like:



      ALTER FUNCTION myschema.f_myfunc(anyarray, anyelement) OWNER TO myrole;


      I get an error message for every ALTER FUNCTION like that:




      ERROR:  improper qualified name (too many dotted names)



      Trying the same in psql produces the same error. Even with the simplest form:



      ALTER FUNCTION foo() OWNER TO myrole;


      There are no dotted names. I found similar complaints here:
      https://forums.aws.amazon.com/thread.jspa?messageID=872096&tstart=0



      Must be a bug in Aurora - or am I missing something?










      share|improve this question
















      Working with Amazon Aurora Postgres Version 2.0, which is basically PostgreSQL 10.4 with a modified storage layer.



      Trying to restore a dump that contains multiple lines like:



      ALTER FUNCTION myschema.f_myfunc(anyarray, anyelement) OWNER TO myrole;


      I get an error message for every ALTER FUNCTION like that:




      ERROR:  improper qualified name (too many dotted names)



      Trying the same in psql produces the same error. Even with the simplest form:



      ALTER FUNCTION foo() OWNER TO myrole;


      There are no dotted names. I found similar complaints here:
      https://forums.aws.amazon.com/thread.jspa?messageID=872096&tstart=0



      Must be a bug in Aurora - or am I missing something?







      postgresql aws-aurora






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 14 '18 at 15:47







      Erwin Brandstetter

















      asked Nov 14 '18 at 15:41









      Erwin BrandstetterErwin Brandstetter

      92.9k9178292




      92.9k9178292






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Response from AWS Support




          On further researching, I was able to find that this was a known issue in Aurora Version 2.0 (compatible with 10.4) and the issue has been fixed on Aurora Version 2.1 ( compatible with PostgreSQL 10.5). I tried testing on my Aurora PostgreSQL 10.5 test cluster to confirm if the issue has been fixed and I was able to successfully execute the statement without any error message.




          tl;dr Bug in Aurora 2.0 (PostgreSQL 10.4), fixed in Aurora 2.1 (PostgreSQL 10.5).





          share























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "182"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f222539%2ferror-improper-qualified-name-too-many-dotted-names-when-trying-alter-functio%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Response from AWS Support




            On further researching, I was able to find that this was a known issue in Aurora Version 2.0 (compatible with 10.4) and the issue has been fixed on Aurora Version 2.1 ( compatible with PostgreSQL 10.5). I tried testing on my Aurora PostgreSQL 10.5 test cluster to confirm if the issue has been fixed and I was able to successfully execute the statement without any error message.




            tl;dr Bug in Aurora 2.0 (PostgreSQL 10.4), fixed in Aurora 2.1 (PostgreSQL 10.5).





            share




























              0














              Response from AWS Support




              On further researching, I was able to find that this was a known issue in Aurora Version 2.0 (compatible with 10.4) and the issue has been fixed on Aurora Version 2.1 ( compatible with PostgreSQL 10.5). I tried testing on my Aurora PostgreSQL 10.5 test cluster to confirm if the issue has been fixed and I was able to successfully execute the statement without any error message.




              tl;dr Bug in Aurora 2.0 (PostgreSQL 10.4), fixed in Aurora 2.1 (PostgreSQL 10.5).





              share


























                0












                0








                0







                Response from AWS Support




                On further researching, I was able to find that this was a known issue in Aurora Version 2.0 (compatible with 10.4) and the issue has been fixed on Aurora Version 2.1 ( compatible with PostgreSQL 10.5). I tried testing on my Aurora PostgreSQL 10.5 test cluster to confirm if the issue has been fixed and I was able to successfully execute the statement without any error message.




                tl;dr Bug in Aurora 2.0 (PostgreSQL 10.4), fixed in Aurora 2.1 (PostgreSQL 10.5).





                share













                Response from AWS Support




                On further researching, I was able to find that this was a known issue in Aurora Version 2.0 (compatible with 10.4) and the issue has been fixed on Aurora Version 2.1 ( compatible with PostgreSQL 10.5). I tried testing on my Aurora PostgreSQL 10.5 test cluster to confirm if the issue has been fixed and I was able to successfully execute the statement without any error message.




                tl;dr Bug in Aurora 2.0 (PostgreSQL 10.4), fixed in Aurora 2.1 (PostgreSQL 10.5).






                share











                share


                share










                answered 1 min ago









                Paul DraperPaul Draper

                1664




                1664






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Database Administrators Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f222539%2ferror-improper-qualified-name-too-many-dotted-names-when-trying-alter-functio%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Anexo:Material bélico de la Fuerza Aérea de Chile Índice Aeronaves Defensa...

                    Always On Availability groups resolving state after failover - Remote harden of transaction...

                    update json value to null Announcing the arrival of Valued Associate #679: Cesar Manara ...