| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Tristan Partin <tristan(at)partin(dot)io>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add editorconfig support for Postgres spec files |
| Date: | 2026-04-17 08:18:22 |
| Message-ID: | 29230792-69b4-473c-b2a7-7801bc8769e0@iki.fi |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 17/04/2026 00:49, Tristan Partin wrote:
> I was reading through some spec files today, and my editor was resolving
> the tab width as 8. I looked at some of the spec files, and we seem to
> have standardized on a tab width of 4 with tabs expanded into spaces.
There's a mix of styles in different files. To pick a few random examples:
src/test/isolation/specs/nowait.spec: indented with 2 spaces. But there
are some tabs too.
src/test/modules/injection_points/specs/repack_toast.spec: Tabs
src/test/modules/brin/specs/summarization-and-inprogress-insertion.spec:
Mix of tabs and spaces, width 4.
Yeah, it would be nice to standardize on something...
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2026-04-17 08:45:53 | Re: EXCEPT TABLE - Case inconsistency for describe \d and \dRp+ |
| Previous Message | jian he | 2026-04-17 08:13:28 | Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column |