@@ -2,6 +2,7 @@
 using Npgsql.BackendMessages;
 using Npgsql.Internal.TypeHandling;
 using Npgsql.PostgresTypes;
+using Npgsql.Properties;
 using NpgsqlTypes;
 
 namespace Npgsql.Internal.TypeHandlers.DateTimeHandlers;
@@ -31,7 +32,7 @@ public override TimeSpan Read(NpgsqlReadBuffer buf, int len, FieldDescription? f
         var months = buf.ReadInt32();
 
         if (months > 0)
-            throw new InvalidCastException("Cannot convert interval value with non-zero months to TimeSpan");
+            throw new InvalidCastException(NpgsqlStrings.CannotReadIntervalWithMonthsAsTimeSpan);
 
         return new(microseconds * 10 + days * TimeSpan.TicksPerDay);
     }
 
@@ -51,4 +51,7 @@
     <data name="CannotSpecifyTargetSessionAttributes" xml:space="preserve">
         <value>When creating a multi-host data source, TargetSessionAttributes cannot be specified. Create without TargetSessionAttributes, and then obtain DataSource wrappers from it. Consult the docs for more information.</value>
     </data>
+    <data name="CannotReadIntervalWithMonthsAsTimeSpan" xml:space="preserve">
+        <value>Cannot read interval values with non-zero months as TimeSpan, since that type doesn't support months. Consider using NodaTime Period which better corresponds to PostgreSQL interval, or read the value as NpgsqlInterval, or transform the interval to not contain months or years in PostgreSQL before reading it.</value>
+    </data>
 </root>