![]() In most cases this will result in few changes in the parsing of text. This ancient backwards-compatibility hack was agreed to have outlived its usefulness.įix the default text search parser to allow leading digits in email and host tokens (Artur Zakirov) Remove PL/pgSQL's "feature" that suppressed the innermost line of CONTEXT for messages emitted by RAISE commands (Pavel Stehule) Also, throw the expected error for bad field names. Make it return infinity or -infinity as appropriate when the requested field is one that is monotonically increasing (e.g, year, epoch), or NULL when it is not (e.g., day, hour). ![]() Historically the extract() function just returned zero given an infinite timestamp, regardless of the given field name. Make extract() behave more reasonably with infinite inputs (Vitaly Burovoy) In to_char(), do not count a minus sign (when needed) as part of the field width for time-related fields (Bruce Momjian)įor example, to_char('-4 years'::interval, 'YY') now returns -04, rather than -4. These changes replace the waiting column with wait_event_type and wait_event. Also, the type of lock being waited for is now visible. Now waits for lightweight locks and buffer pins are also shown in pg_stat_activity. Historically a process has only been shown as waiting if it was waiting for a heavyweight lock. Improve the pg_stat_activity view's information about what a process is waiting for (Amit Kapila, Ildus Kurbangaliev) Version 9.6 contains a number of changes that may affect compatibility with previous releases. A dump/restore using pg_dumpall, or use of pg_upgrade, is required for those wishing to migrate data from any previous release. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |