release: v0.4.0

[cutecutecat]

The update from 0.3.0 to 0.4.0 might fail!

Due to a conflict definition of _vectors_svecf32_in at 0.3.0:

_vectors_svecf32_in(input, oid, _typmod)

and at 0.2.1--0.3.0:

_vectors_svecf32_in(input, oid, typmod)

As 0.4.0 picks latter signature, and PostgreSQL doesn't support parameter name changing.

Therefore the update route of 0.2.1 -> 0.3.0 -> 0.4.0 can succeed, but 0.3.0 -> 0.4.0 would fail.

Ref: L744 of file sql/upgrade/vectors--0.3.0--0.4.0.sql

Conclusion

Check and Keep these two signatures as their own.

[usamoi]

Due to a conflict definition of _vectors_svecf32_in at 0.3.0:

Why? I cannot see.

pgvecto.rs/sql/install/vectors--0.3.0.sql

Lines 859 to 866 in cc4776f

	CREATE FUNCTION "_vectors_svecf32_in"(
	"input" cstring, /* &core::ffi::c_str::CStr */
	"_oid" oid, /* pgrx_pg_sys::submodules::oids::Oid */
	"typmod" INT /* i32 */
	) RETURNS svector /* vectors::datatype::memory_svecf32::SVecf32Output */
	IMMUTABLE STRICT PARALLEL SAFE
	LANGUAGE c /* Rust */
	AS 'MODULE_PATHNAME', '_vectors_svecf32_in_wrapper';

. The parameter name is typmod.

pgvecto.rs/sql/upgrade/vectors--0.2.1--0.3.0.sql

Lines 345 to 350 in cc4776f

	CREATE FUNCTION "_vectors_svecf32_in"(
	"input" cstring,
	"_oid" oid,
	"typmod" INT
	) RETURNS svector
	IMMUTABLE STRICT PARALLEL SAFE LANGUAGE c AS 'MODULE_PATHNAME', '_vectors_svecf32_in_wrapper';

. The parameter name is typmod.