How to Install and Uninstall postgresql11-plr Package on openSuSE Tumbleweed

Last updated: May 02,2024

Deprecated! Installation of this package may no longer be supported.

1. Install "postgresql11-plr" package

Please follow the step by step instructions below to install postgresql11-plr on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                postgresql11-plr
            
                    
    
    Copied

2. Uninstall "postgresql11-plr" package

This guide let you learn how to uninstall postgresql11-plr on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                postgresql11-plr
            
                    
    
    Copied

3. Information about the postgresql11-plr package on openSuSE Tumbleweed

Information for package postgresql11-plr:
-----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : postgresql11-plr
Version : 8.4.1-1.3
Arch : x86_64
Vendor : openSUSE
Installed Size : 96,2 KiB
Installed : No
Status : not installed
Source package : postgresql11-plr-8.4.1-1.3.src
Summary : PL/R - R Procedural Language for PostgreSQL
Description :
PL/R is a loadable procedural language that enables you to write PostgreSQL
functions and triggers in the R programming language. PL/R offers most (if
not all) of the capabilities a function writer has in the R language.
Commands are available to access the database via the PostgreSQL Server
Programming Interface (SPI) and to raise messages via elog() . There is no
way to access internals of the database backend. However the user is able
to gain OS-level access under the permissions of the PostgreSQL user ID,
as with a C function. Thus, any unprivileged database user should not be
permitted to use this language. It must be installed as an untrusted
procedural language so that only database superusers can create functions
in it. The writer of a PL/R function must take care that the function cannot
be used to do anything unwanted, since it will be able to do anything that
could be done by a user logged in as the database administrator.
An implementation restriction is that PL/R procedures cannot be used to
create input/output functions for new data types.