mirror of
				https://github.com/postgres/postgres.git
				synced 2025-10-25 13:17:41 +03:00 
			
		
		
		
	This isn't fully tested as yet, in particular I'm not sure that the "foo--unpackaged--1.0.sql" scripts are OK. But it's time to get some buildfarm cycles on it. sepgsql is not converted to an extension, mainly because it seems to require a very nonstandard installation process. Dimitri Fontaine and Tom Lane
		
			
				
	
	
		
			29 lines
		
	
	
		
			643 B
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			29 lines
		
	
	
		
			643 B
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
| --
 | |
| -- init pgcrypto
 | |
| --
 | |
| CREATE EXTENSION pgcrypto;
 | |
| -- ensure consistent test output regardless of the default bytea format
 | |
| SET bytea_output TO escape;
 | |
| -- check for encoding fn's
 | |
| SELECT encode('foo', 'hex');
 | |
|  encode 
 | |
| --------
 | |
|  666f6f
 | |
| (1 row)
 | |
| 
 | |
| SELECT decode('666f6f', 'hex');
 | |
|  decode 
 | |
| --------
 | |
|  foo
 | |
| (1 row)
 | |
| 
 | |
| -- check error handling
 | |
| select gen_salt('foo');
 | |
| ERROR:  gen_salt: Unknown salt algorithm
 | |
| select digest('foo', 'foo');
 | |
| ERROR:  Cannot use "foo": No such hash algorithm
 | |
| select hmac('foo', 'foo', 'foo');
 | |
| ERROR:  Cannot use "foo": No such hash algorithm
 | |
| select encrypt('foo', 'foo', 'foo');
 | |
| ERROR:  Cannot use "foo": No such cipher algorithm
 |