market - Search results in mailing lists
Mailing lists >> pgsql-hackers >> Thread
2025-03-29 17:40:55 | Re: in BeginCopyTo make materialized view using COPY TO instead of COPY (query). (David G. Johnston)
marketed as a general purpose export facility. While copy {relation} from is a general purpose
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (2)
2024-06-13 19:16:54 | Re: RFC: adding pytest as a supported test framework (Greg Sabino Mullane)
marketing problem. I've not seen any dire requests for help come across on the lists
Mailing lists >> pgsql-hackers >> Thread
2024-05-15 12:26:45 | Re: Converting README documentation to Markdown (Daniel Gustafsson)
market presence. For offline work I targeted rendering with pandoc since we already have a dependency
Mailing lists >> pgsql-hackers >> Thread
2024-03-18 23:34:23 | Re: documentation structure (Robert Haas)
marketing materials, and the smaller of which has "utility functions" like "login", "contact us", and "search
Mailing lists >> pgsql-hackers >> Thread
2023-10-22 19:23:30 | Re: Guiding principle for dropping LLVM versions? (Thomas Munro)
marketing wanted the compiler's version numbers to align with xcode's version numbers? they
Mailing lists >> pgsql-hackers >> Thread
2023-09-07 11:44:11 | Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~? (Daniel Gustafsson)
said, my gut feeling is that 3.x has gotten pretty good market penetration. -- Daniel Gustafsson
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (2)
2023-05-25 08:55:57 | AW: Proposal: Removing 32 bit support starting from PG17++ (Hans Buschmann)
markets. Therefore I spoke from inspiration by Intel's move, what does not implicitely indicate
Mailing lists >> pgsql-hackers >> Thread
2023-04-14 15:25:34 | Re: Should we remove vacuum_defer_cleanup_age? (Greg Stark)
marketing or sales organizations or in some cases infosec teams and consume data from lots
Mailing lists >> pgsql-hackers >> Thread
2023-04-11 09:27:17 | Re: User functions for building SCRAM secrets (Magnus Hagander)
marketed, for good reasons, SCRAM as a way to finally make postgres *not* do this
Mailing lists >> pgsql-hackers >> Thread
2023-03-26 15:19:18 | Re: Disable vacuuming to provide data history (Hannu Krosing)
market
---
Hannu
On Sat, Feb 25, 2023 at 3:11 AM Vik Fearing
Mailing lists >> pgsql-hackers >> Thread
2022-11-01 15:19:02 | Re: heavily contended lwlocks with long wait queues scale badly (Jonathan S. Katz)
marketing opportunities to discuss this (though I'm sure there will be plenty of blog
Mailing lists >> pgsql-hackers >> Thread
2022-08-26 03:45:10 | Re: use ARM intrinsics in pg_lfind32() where available (John Naylor)
markets may support the following combinations: No NEON or floating-point. Full floating-point and SIMD
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (3)
2022-05-20 05:53:12 | Re: Skipping schema changes in publication (Peter Smith)
marketing, sales; + + Alter publication production_publication to publish + all tables except users and + departments tables
Mailing lists >> pgsql-hackers >> Thread
2022-02-15 22:37:07 | Re: Observability in Postgres (Magnus Hagander)
market has spoken and said they accept that one. Yeah, it's clearly designed around
Mailing lists >> pgsql-hackers >> Thread
2022-01-13 04:51:56 | Custom Operator for citext LIKE predicates question (Efrain J. Berdecia)
Marketing and Communications'::citext) OR (c1000000001 = 'Ericsson Master Data Management'::citext) OR (c1000000001 = 'Mrictton OHS'::citext