Re: Re: reloption to prevent VACUUM from truncating empty pages at the end of relation
Le 5 avril 2019 20:11:38 GMT+02:00, Julien Rouhaud a écrit : >On Fri, Apr 5, 2019 at 7:04 PM Robert Haas >wrote: >> > >> My preference is for "truncate" over "shrink". > >I don't really like "shrink" either, but users already have problems >to get the difference between VACUUM and VACUUM FULL, I'm afraid that >"VACUUM TRUNCATE_TABLE" will just make things worse. How about TRIM? -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Re: Log a sample of transactions
Le 4 janvier 2019 13:20:09 GMT+01:00, Peter Eisentraut a écrit : >On 12/12/2018 22:32, Adrien Nayrat wrote: >> Per idea of Nikolay Samokhvalov[1] I propose this patch to add the >possibility >> to log all statements from a fraction of transactions. >> >> I have several questions: >> * Do we want this feature? > >It's not clear to me what the use is. The per-statement sampling >allows >you to capture slow queries without overwhelming the logs. We don't >have any logging of slow transactions or any other transaction scope >logging, so what will this sample? > >-- >Peter Eisentraut http://www.2ndQuadrant.com/ >PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services Hello, When you troubleshoot applicative issues with multi-statements transaction, you may have to log all queries to find all statements of one transaction. With high throughput, it could be hard to log all queries without causing troubles. The goal of this patch is to be able to log a sample of transactions. I agree the use case is specific. Regards -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Re: New GUC to sample log queries
Le 4 janvier 2019 13:16:48 GMT+01:00, Peter Eisentraut a écrit : >On 19/11/2018 14:40, Tomas Vondra wrote: >> On 11/19/18 2:57 AM, Michael Paquier wrote: >>> On Sun, Nov 18, 2018 at 12:18:33PM +0100, Dmitry Dolgov wrote: Since it's hard to come up with a concise name that will mention >sampling rate in the context of min_duration_statement, I think it's fine to name >this configuration "log_sample_rate", as long as it's dependency from log_min_duration_statements is clearly explained in the >documentation. >>> >>> log_sample_rate looks fine to me as a name. >> >> That seems far too short to me - the name should indicate it applies >to >> statement logging. I'd say log_statement_sample_rate is better. > >It was committed with this name, but then one has to wonder why it >doesn't also apply to log_statement. > >-- >Peter Eisentraut http://www.2ndQuadrant.com/ >PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services Yes, but maybe log_min_duration_statements_sample is too long? -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Re: New committers announced at PGCon 2018
Le 1 juin 2018 23:54:28 GMT+02:00, Julien Rouhaud a écrit : >On Fri, Jun 1, 2018 at 11:22 PM, Joe Conway wrote: >> On 06/01/2018 05:14 PM, Andres Freund wrote: >>> On 2018-06-01 17:05:11 -0400, Tom Lane wrote: The core team is pleased to announce the appointment of seven new Postgres committers: Etsuro Fujita Peter Geoghegan Amit Kapila Alexander Korotkov Thomas Munro Michael Paquier Tomas Vondra Congratulations to all! >>> >>> +1! >> >> +7! > >Congrats to all! +1, good for community and postgresql! -- Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
