pg 1.3.0.rc2-x64-mingw32 → 1.3.0.rc3-x64-mingw32

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 41acb016111b1a403c907386e51811541869bacec6523042e95491def8b820d3
-  data.tar.gz: 00c0d9ceddda6fe84b6fe1ccb1561a566c3c380ad6b9c35009e596b4df773229
+  metadata.gz: 1c8dd86a0ff7573d4ee5160db7ba24bfcb8a60b0b8a1f8ba024c4f4df4f474ce
+  data.tar.gz: 267098a841b2930912910d7ff679d74224f5f7e45dc3636b7151ad7f513ca40d
 SHA512:
-  metadata.gz: 2bcc301c930009cef1586d590ce1b84e2afa3ce96c8fbb69e33cc93732d4862e7001f1a5a0fa687eb1436359e8984fdb7ddba86d83af9c9df66aad40e42f1343
-  data.tar.gz: cba31ff2d6a877e288022d7bb6c7ebf56641f6483275606ed1645758f009bbe58e90c002cb85cd6ddb573916cc540ed754a322e6915d8264c82fd03f45de50b0
+  metadata.gz: 2141632efe8c5ef6442d960d6d0e4351ba019cf7bdfe894d8feec6b55b3daa218a1e652c66005f4deb073508c8357d8f7f85b13fff73eb713ecc3f65e9825c82
+  data.tar.gz: 1d937df566d35602d7e75c6b82552fdfc774519fd9725f7679ead731160f20592944f9dd1bc147a7b4a2fb1fbaee12f236c8225e2d42f8a4fc3cd26d10ec4bb9

checksums.yaml.gz.sig

@@ -1,2 +1,2 @@
-U�l���<�����l�
�S+�P���٢M��q��eC�	�o
��OH1%�ڤ�>��UvQ9�1�\<��/IQ�~&��!�(U v\"�&��vH튢�g��D&�u(���/ʿ+r�%�^�|�`(�t�u]���I��X���A5�r��٨��cY���pT5���D_����nW=�|ՊC�z��U
-�jv����Cމ'��m_{�:�COʰ�z��&(�\m;�䕀&�ޢ�DM�5��H	�5g��ft`��vn
�X�m%�1�n�(b�r��y��`�����e��������u��
%��
+l}J���쁩"�DB�#��^���^3�=ϯ=���l���_�B���4"fd����/qE���羞�����(�y.�Vp��2^CQ�5�Ő��Qa�:Bζ��}�B�"w�Z&=��>�n-x�F�L�� ��;>�uTP��H����_^���꺧�a�¼җ��������S�s�%��ChX�2'�=j��v����q���]�jW]�'�V����AW�c��}����ᶆ���*O�5S�ŜTΆF�n�����iH�M"���W͇���j9t�(i�b�l�Jp��F���d߂�8�\�B�VI+��狁�/,K����1�U�q��@=p��h���KD
+H��n$�I^���g�!�=V$*=Vwi���>!

data/.github/workflows/source-gem.yml

@@ -113,7 +113,6 @@ jobs:
       - run: bundle install
 
       - run: gem install --local *.gem --verbose
-        continue-on-error: ${{ matrix.ruby == 'truffleruby-head' }}
 
       - name: Run specs
         continue-on-error: ${{ matrix.ruby == 'truffleruby-head' }}

data/ext/pg_connection.c

@@ -968,8 +968,8 @@ static VALUE pgconn_sync_exec_params( int, VALUE *, VALUE );
  * However #async_exec has two advantages:
  *
  * 1. #async_exec can be aborted by signals (like Ctrl-C), while #exec blocks signal processing until the query is answered.
- * 2. Ruby VM gets notified about IO blocked operations.
- *    It can therefore schedule things like garbage collection, while queries are running like in this proposal: https://bugs.ruby-lang.org/issues/14723
+ * 2. Ruby VM gets notified about IO blocked operations and can pass them through <tt>Fiber.scheduler</tt>.
+ *    So only <tt>async_*</tt> methods are compatible to event based schedulers like the async gem.
  */
 static VALUE
 pgconn_sync_exec(int argc, VALUE *argv, VALUE self)
@@ -2208,17 +2208,25 @@ pgconn_notifies(VALUE self)
 }
 
 
-#if !defined(HAVE_RB_IO_WAIT)
+#if defined(HAVE_RB_IO_WAIT)
+
+/* Use our own function and constants names, to avoid conflicts with truffleruby-head on its road to ruby-3.0 compatibility. */
+#define pg_rb_io_wait rb_io_wait
+#define PG_RUBY_IO_READABLE RUBY_IO_READABLE
+#define PG_RUBY_IO_WRITABLE RUBY_IO_WRITABLE
+#define PG_RUBY_IO_PRIORITY RUBY_IO_PRIORITY
+
+#else
 /* For compat with ruby < 3.0 */
 
 typedef enum {
-    RUBY_IO_READABLE = RB_WAITFD_IN,
-    RUBY_IO_WRITABLE = RB_WAITFD_OUT,
-    RUBY_IO_PRIORITY = RB_WAITFD_PRI,
-} rb_io_event_t;
+    PG_RUBY_IO_READABLE = RB_WAITFD_IN,
+    PG_RUBY_IO_WRITABLE = RB_WAITFD_OUT,
+    PG_RUBY_IO_PRIORITY = RB_WAITFD_PRI,
+} pg_rb_io_event_t;
 
 static VALUE
-rb_io_wait(VALUE io, VALUE events, VALUE timeout) {
+pg_rb_io_wait(VALUE io, VALUE events, VALUE timeout) {
 	rb_io_t *fptr;
 	struct timeval waittime;
 	int res;
@@ -2267,7 +2275,7 @@ wait_socket_readable( VALUE self, struct timeval *ptimeout, void *(*is_readable)
 		/* Is the given timeout valid? */
 		if( !ptimeout || (waittime.tv_sec >= 0 && waittime.tv_usec >= 0) ){
 			/* Wait for the socket to become readable before checking again */
-			ret = rb_io_wait(socket_io, RB_INT2NUM(RUBY_IO_READABLE), wait_timeout);
+			ret = pg_rb_io_wait(socket_io, RB_INT2NUM(PG_RUBY_IO_READABLE), wait_timeout);
 		} else {
 			ret = Qfalse;
 		}
@@ -2304,9 +2312,9 @@ pgconn_async_flush(VALUE self)
 		/* wait for the socket to become read- or write-ready */
 		int events;
 		VALUE socket_io = pgconn_socket_io(self);
-		events = RB_NUM2INT(rb_io_wait(socket_io, RB_INT2NUM(RUBY_IO_READABLE | RUBY_IO_WRITABLE), Qnil));
+		events = RB_NUM2INT(pg_rb_io_wait(socket_io, RB_INT2NUM(PG_RUBY_IO_READABLE | PG_RUBY_IO_WRITABLE), Qnil));
 
-		if (events & RUBY_IO_READABLE)
+		if (events & PG_RUBY_IO_READABLE)
 			pgconn_consume_input(self);
 	}
 	return Qtrue;
@@ -3013,10 +3021,10 @@ pgconn_discard_results(VALUE self)
 		int status;
 
 		/* pgconn_block() raises an exception in case of errors.
-		* To avoid this call rb_io_wait() and PQconsumeInput() without rb_raise().
+		* To avoid this call pg_rb_io_wait() and PQconsumeInput() without rb_raise().
 		*/
 		while( gvl_PQisBusy(conn) ){
-			rb_io_wait(socket_io, RB_INT2NUM(RUBY_IO_READABLE), Qnil);
+			pg_rb_io_wait(socket_io, RB_INT2NUM(PG_RUBY_IO_READABLE), Qnil);
 			if ( PQconsumeInput(conn) == 0 ) {
 				pgconn_close_socket_io(self);
 				return Qfalse;
@@ -3037,7 +3045,7 @@ pgconn_discard_results(VALUE self)
 				int st = gvl_PQgetCopyData(conn, &buffer, 1);
 				if( st == 0 ) {
 					/* would block -> wait for readable data */
-					rb_io_wait(socket_io, RB_INT2NUM(RUBY_IO_READABLE), Qnil);
+					pg_rb_io_wait(socket_io, RB_INT2NUM(PG_RUBY_IO_READABLE), Qnil);
 					if ( PQconsumeInput(conn) == 0 ) {
 						pgconn_close_socket_io(self);
 						return Qfalse;
@@ -3076,6 +3084,7 @@ pgconn_discard_results(VALUE self)
  * #exec is an alias for #async_exec which is almost identical to #sync_exec .
  * #sync_exec is implemented on the simpler synchronous command processing API of libpq, whereas
  * #async_exec is implemented on the asynchronous API and on ruby's IO mechanisms.
+ * Only #async_exec is compatible to <tt>Fiber.scheduler</tt> based asynchronous IO processing introduced in ruby-3.0.
  * Both methods ensure that other threads can process while waiting for the server to
  * complete the request, but #sync_exec blocks all signals to be processed until the query is finished.
  * This is most notably visible by a delayed reaction to Control+C.

data/lib/pg/connection.rb

@@ -21,6 +21,13 @@ require 'socket'
 #
 # See the PG::Result class for information on working with the results of a query.
 #
+# Many methods of this class have three variants kind of:
+# 1. #exec - the base method which is an alias to #async_exec .
+#    This is the method that should be used in general.
+# 2. #async_exec - the async aware version of the method, implemented by libpq's async API.
+# 3. #sync_exec - the method version that is implemented by blocking function(s) of libpq.
+#
+# Sync and async version of the method can be switched by Connection.async_api= , however it is not recommended to change the default.
 class PG::Connection
 
 	# The order the options are passed to the ::connect method.
@@ -690,7 +697,7 @@ class PG::Connection
 		#
 		# Raises a PG::Error if the connection fails.
 		def new(*args, **kwargs)
-			conn = PG::Connection.connect_start(*args, **kwargs ) or
+			conn = self.connect_start(*args, **kwargs ) or
 				raise(PG::Error, "Unable to create a new connection")
 
 			raise(PG::ConnectionBad, conn.error_message) if conn.status == PG::CONNECTION_BAD

data/lib/pg/version.rb

@@ -1,4 +1,4 @@
 module PG
 	# Library version
-	VERSION = '1.3.0.rc2'
+	VERSION = '1.3.0.rc3'
 end

data/lib/pg.rb

@@ -63,8 +63,8 @@ module PG
 
 
 	### Convenience alias for PG::Connection.new.
-	def self::connect( *args )
-		return PG::Connection.new( *args )
+	def self::connect( *args, **kwargs )
+		return PG::Connection.new( *args, **kwargs )
 	end
 
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: pg
 version: !ruby/object:Gem::Version
-  version: 1.3.0.rc2
+  version: 1.3.0.rc3
 platform: x64-mingw32
 authors:
 - Michael Granger
@@ -36,7 +36,7 @@ cert_chain:
   d5T9wAD7jW/0seVujw+76/YOJWO3Dft+FQmMBbdd8s3J47HbN9R2mDt6fl6he+X/
   gw==
   -----END CERTIFICATE-----
-date: 2022-01-08 00:00:00.000000000 Z
+date: 2022-01-13 00:00:00.000000000 Z
 dependencies: []
 description: Pg is the Ruby interface to the PostgreSQL RDBMS. It works with PostgreSQL
   9.3 and later.