Re: Using 9.6 client with 10.0 server

>are there any drawbacks in using 9.6 client with 10.0 server?

A simple declarative partitioning example for the differences:

root(at)a5c0a6414f2e:/# psql
psql (10.1)
Type "help" for help.

test=# CREATE TABLE measurement (
test(# city_id int not null,
test(# logdate date not null,
test(# peaktemp int,
test(# unitsales int
test(# ) PARTITION BY RANGE (logdate);
CREATE TABLE
test=#
test=# CREATE TABLE measurement_y2006m02 PARTITION OF measurement
test-# FOR VALUES FROM ('2006-02-01') TO ('2006-03-01');
CREATE TABLE
test=# \d+
List of relations
Schema | Name | Type | Owner | Size | Description
--------+----------------------+-------+-------+---------+-------------
public | measurement | table | test | 0 bytes |
public | measurement_y2006m02 | table | test | 0 bytes |
(2 rows)

Connecting from 9.6 - I can see only 1 table

root(at)cf0ddd0a1d58:/# psql
psql (9.6.6, server 10.1)
*WARNING: psql major version 9.6, server major version 10.*
* Some psql features might not work.*
Type "help" for help.

test=# \d+
List of relations
Schema | Name | Type | Owner | Size | Description
--------+----------------------+-------+-------+---------+-------------
public | measurement_y2006m02 | table | test | 0 bytes |
(1 row)

Regards,
Imre

2018-01-11 14:15 GMT+01:00 Imre Samu <pella(dot)samu(at)gmail(dot)com>:

> >are there any drawbacks in using 9.6 client with 10.0 server?
>
> imho: you have to re-check the new improvements[1] :
> some examples:
> * "Declarative table partitioning" ( as I know, you can't see all
> information from psql9.6 )
> * "Stronger password authentication based on SCRAM-SHA-256" ( if the
> security is the first priority )
>
> scram-sha-256
> The method scram-sha-256performs SCRAM-SHA-256 authentication, as
> described in RFC 7677. It is a challenge-response scheme that prevents
> password sniffing on untrusted connections and supports storing passwords
> on the server in a cryptographically hashed form that is thought to be
> secure.
> *This is the most secure of the currently provided methods, but it is not
> supported by older client libraries.*
> https://www.postgresql.org/docs/10/static/auth-methods.html
>
> * changes in sequences ( "a new pg_sequence system catalog" ; *"The
> output of psql's \d command for a sequence has been redesigned, too." * )
> * changes in "psql" Client Application
>
> [1] https://www.postgresql.org/docs/10/static/release-10.html
>
> Regards,
> Imre
>
>
> 2018-01-11 11:14 GMT+01:00 Ronnj Grotto <ronnj(dot)grotto(at)texa(dot)com>:
>
>> Hello,
>>
>> are there any drawbacks in using 9.6 client with 10.0 server?
>>
>> Thank you in advance.
>>
>>
>>
>>
>> *Ronnj Grotto *DATABASE ADMIN
>> ronnj(dot)grotto(at)texa(dot)com
>> Diretto: 0422.79.16.85
>> Interno: 1685
>>
>> <http://www.facebook.com/TEXAcom> <http://www.youtube.com/TEXAcom>
>>
>>
>> *TEXA S.p.A. *Sede Legale: Via 1 Maggio, 9 - 31050 Monastier di Treviso
>> - ITALY
>> <https://maps.google.com/?q=Via+1+Maggio,+9+-+31050+Monastier+di+Treviso+-+ITALY&entry=gmail&source=g>
>> Stabilimento e Sede Amministrativa: Via Vallio - 31050 Monastier di
>> Treviso - ITALY
>> Cod. Fisc.- N.I. Registro Imprese di Treviso - Part. IVA: 02413550266
>> Capitale Sociale 1.000.000 € i.v. - R.E.A. N. 208102
>> Società con socio unico e soggetta ad attività di direzione e
>> coordinamento di Opera Holding S.r.l.
>> Phone +39 0422.791.311
>> Fax +39 0422.791.300
>> www.texa.com
>>
>> CONFIDENTIALITY NOTICE
>> This message and its attachments are addressed solely to the persons
>> above and may contain confidential information.
>> If you have received the message in error, be informed that any use of
>> the content here of is prohibited.
>> Please return it immediately to the sender and delete the message.
>> P Please consider the environment before printing this e-mail.
>>
>>
>>
>
>