pg 1.3.5 → 1.4.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 0bb3782224d0c471417ceaa47d1355d5a06be2590fb3671fde73882346db0c5c
4
- data.tar.gz: cd728b238d0b174f02a31c38afbd990177f81eec8516a1c953ee7bade1ddb4c6
3
+ metadata.gz: de283e26d9b321e332b3a0cfb7528a169c85c6842b45eed15a11dceafff0c51c
4
+ data.tar.gz: 32969355bf10d56fcc23611b5906c93315acd90dc718c13db77adb5358e8a2c6
5
5
  SHA512:
6
- metadata.gz: d7b3ad8293281fb830274dc0e3d6e3c59c1dca85ea4f112f0aaf3a7629f61e315747f1e6ecad96e7a9528d42eeb3baafb819b7360d02acfc636ae7cb2d24ef42
7
- data.tar.gz: f2476f2c7b1950346adf87c3675b838b9c57c909d6d787b50f4cf418ccb51296a02677faac7910378a665daa087f2aa552375f72ca42ba428e539cf07e80392c
6
+ metadata.gz: 9c85938f84751d4720b1419cf17cc089804f6ae64af363078267e784a04a99b04e8c5448d5ac349afb833254e8991f619fe2b3eb2492e2b91fdd446c2f42797a
7
+ data.tar.gz: 96777364ae066e8a06b0c0d589752f4f328fd17066b7888663f45798207a6737c68fef01fa10cba6ae7f210a7f6dd8c55210039cbd4d9b71b91a709b3a052fdd
checksums.yaml.gz.sig CHANGED
@@ -1,4 +1,2 @@
1
- ��`��<� .B� /m��u��+�
2
- 8�e㽟���P\'����+�f&̮�.M4��Sz��t�<���<�V���#�$��4��52(mK���� .��D�UĹh��(�(������6�c��C��b+��?T���x���(�gd�i�K��%�vD�0H�kK�)�G2"ތ6::Z!�2��3Be�$r�uo��K�d,_���������\���E� �|����eĘ����!2@�僑 *4����BT+ګ�m*Zp6��
3
- �NNȼ�<�m9A@�����
4
- ~$�|��ذyB�R�vfj�=d+�j6m��&�B1��:���2<�+���!��� �܎�+��Q���\��d�e'/�JR��r�vF�
1
+ ��aD���ns�ScĬ�0h�,�Ë;�&[\*��h�U6�����†J�'�F��\ j�yP����~�"��6Ǝ�����B\H,���LP! >ݢ��=�����/y��f+��k4�M]�`�AEa����yH�22yˎ�p���I�Gz�A�KѻT���z��u@�
2
+ ��j�+>\��!Ijh灀����'�c{���?V߇o�Z#eKjv����� ��� �;)�
data/History.rdoc CHANGED
@@ -1,3 +1,27 @@
1
+ == v1.4.0 [YYYY-MM-DD] Lars Kanis <lars@greiz-reinsdorf.de>
2
+
3
+ Added:
4
+
5
+ - Add PG::Connection#hostaddr, present since PostgreSQL-12. #453
6
+ - Add PG::Connection.conninfo_parse to wrap PQconninfoParse. #453
7
+
8
+ Bugfixes:
9
+
10
+ - Try IPv6 and IPv4 addresses, if DNS resolves to both. #452
11
+ - Re-add block-call semantics to PG::Connection.new accidently removed in pg-1.3.0. #454
12
+ - Handle client error after all data consumed in #copy_data for output. #455
13
+ - Avoid spurious keyword argument warning on Ruby 2.7. #456
14
+ - Change connection setup to respect connect_timeout parameter. #459
15
+ - Fix indefinite hang in case of connection error on Windows #458
16
+ - Set connection attribute of PG::Error in various places where it was missing. #461
17
+ - Fix transaction leak on early break/return. #463
18
+ - Update Windows fat binary gem to OpenSSL-1.1.1o and PostgreSQL-14.4.
19
+
20
+ Enhancements:
21
+
22
+ - Don't flush at each put_copy_data call, but flush at get_result. #462
23
+
24
+
1
25
  == v1.3.5 [2022-03-31] Lars Kanis <lars@greiz-reinsdorf.de>
2
26
 
3
27
  Bugfixes:
data/Rakefile.cross CHANGED
@@ -31,8 +31,8 @@ class CrossLibrary < OpenStruct
31
31
  self.host_platform = toolchain
32
32
 
33
33
  # Cross-compilation constants
34
- self.openssl_version = ENV['OPENSSL_VERSION'] || '1.1.1m'
35
- self.postgresql_version = ENV['POSTGRESQL_VERSION'] || '14.2'
34
+ self.openssl_version = ENV['OPENSSL_VERSION'] || '1.1.1o'
35
+ self.postgresql_version = ENV['POSTGRESQL_VERSION'] || '14.4'
36
36
 
37
37
  # Check if symlinks work in the current working directory.
38
38
  # This fails, if rake-compiler-dock is running on a Windows box.
data/ext/extconf.rb CHANGED
@@ -1,5 +1,3 @@
1
- # -*- encoding: utf-8 -*-
2
-
3
1
  require 'pp'
4
2
  require 'mkmf'
5
3
 
@@ -169,32 +167,3 @@ end
169
167
  create_header()
170
168
  create_makefile( "pg_ext" )
171
169
 
172
-
173
- def message!(important_message)
174
- message important_message
175
- if !$stdout.tty? && File.chardev?('/dev/tty')
176
- File.open('/dev/tty', 'w') do |tty|
177
- tty.print important_message
178
- end
179
- end
180
- rescue
181
- end
182
-
183
- if "2022-04-01" == Time.now.strftime("%Y-%m-%d")
184
- message! <<-EOM
185
- ===================================================================
186
- HEADS UP! Prepare for pg-1.4.2022 ! 🎉🎉🎉
187
-
188
- Now that psycopg3 has most of the features of ruby-pg, we plan to
189
- switch to using it as our foundation for the next pg release.
190
- It will run through pycall and requires a working python setup.
191
- This will minimize our development and maintenance efforts, since
192
- it allows us to use one and the same code base for both programming
193
- languages - ruby and python. 👏😃
194
-
195
- And we follow the recent merge of the Django and Rails teams! ❤️
196
-
197
- Stay up-to-date at https://github.com/ged/ruby-pg/issues/449
198
- ===================================================================
199
- EOM
200
- end