| From: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Should we remove unused code? |
| Date: | 2016-04-18 15:37:51 |
| Message-ID: | 20160418183751.438b2f00@fujitsu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello, Tom.
Thanks for your reply.
> The fact that make check-world doesn't run any code that uses some
> feature isn't a great argument for removing it. Consider third-party
> extensions, for starters.
What is current policy regarding such sort of things? Is everything
that is in .h files considered a public API and should be backward
compatible? In this case - for how long, forever or until next major
release? Or lets say there is some API that is not used neither
internally nor by any package available on PGXN. Can we break API then?
--
Best regards,
Aleksander Alekseev
http://eax.me/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2016-04-18 15:44:58 | Re: Parser extensions (maybe for 10?) |
| Previous Message | Robert Haas | 2016-04-18 15:35:05 | Re: Spinlocks and semaphores in 9.2 and 9.3 |