Re: bottom / top posting

2021-06-09 Thread Steve Litt
Dean Gibson (DB Administrator) said on Wed, 9 Jun 2021 14:41:47 -0700 >> On Mon, Jun 7, 2021 at 07:53:30PM +0200, Francisco Olarte wrote: >>> ... properly scanning a top posted one takes much longer. > >Not here. Depends on whether the top-poster reiterates nouns instead of just using pronou

Re: bottom / top posting

2021-06-09 Thread Adrian Ho
On 7/6/21 8:05 pm, Vijaykumar Jain wrote: I hear a lot of suggestions wrt bottom / top posting. To be pedantic, the preferred posting style seems in fact to be *inline trim-posting*, i.e. * your responses are immediately below the text you're replying to, so the context is immediately appar

PostgreSQL replication lag - Suggestions and questions

2021-06-09 Thread Lucas
Hi, I have a cluster of PostgreSQL 9.2.21, where there is one master and one slave with streaming replication. I have few points and questions about the replication, and was hopping you guys could share your opinions, suggestions and experiences. > Before I start; Yes! I know... PG 9.2? Really?

Re: bottom / top posting

2021-06-09 Thread Adrian Klaver
On 6/9/21 2:41 PM, Dean Gibson (DB Administrator) wrote: On Mon, Jun 7, 2021 at 07:53:30PM +0200, Francisco Olarte wrote: ... properly scanning a top posted one takes much longer. I wonder about the tolerance of the world we live in.  Somehow, I can deal with top-posting, bottom-posting,

Re: bottom / top posting

2021-06-09 Thread Dave Cramer
> The reason why the old-timers around here are sticky about this is that > we believe we are writing for the mailing list archives. Gmail-style > quoting is indeed the appropriate amount of effort for throwaway threads > that only a few people will read and (probably) none of them will consult >

Re: bottom / top posting

2021-06-09 Thread Tom Browder
On Wed, Jun 9, 2021 at 17:05 Tom Lane wrote: > "Dean Gibson (DB Administrator)" writes: > > Top-posting has been the predominantly common practice in the business & > > government world for decades, & it is easy to adapt to. But it sure adds to the digital clutter! The reason why the old-time

Re: bottom / top posting

2021-06-09 Thread Tom Lane
"Dean Gibson (DB Administrator)" writes: > Top-posting has been the predominantly common practice in the business & > government world for decades, & it is easy to adapt to. The reason why the old-timers around here are sticky about this is that we believe we are writing for the mailing list arc

Re: bottom / top posting

2021-06-09 Thread Dean Gibson (DB Administrator)
On Mon, Jun 7, 2021 at 07:53:30PM +0200, Francisco Olarte wrote: ... properly scanning a top posted one takes much longer. Not here. I find top-posting moderately offensive, like saying "I am not going to waste time to make your reading experience better". Not here either. Top-posting

How to pass a parameter in a query to postgreSQL 12

2021-06-09 Thread Hassan Camacho Cadre
Hello I recently installed a postgreSQL v12, in previous version 8.3 in all my queries I pass parameters using the character : SELECT public.tabla.id FROM public.tabla WHERE public.tabla.id = :a In the new version when I try to make this query it sends me an error ERROR syntax error

Re: bottom / top posting

2021-06-09 Thread Jan Wieck
On 6/7/21 5:40 PM, Joshua Drake wrote: At least the students haven't discovered this list yet and are posting their homework assignments (like they do on chat channels). You forgot to mention that they are posting their homework assignments as cellphone pictures taken from half broken implemen

Re: JDBC error: Unexpected packet type: 25

2021-06-09 Thread Vijaykumar Jain
" java.io.IOException: Unexpected packet type: 25" char 25 is EM. ( End of Medium) I do not see it being part of the wire protocol, as for the same reason, not in pgjdbc handling i think. PostgreSQL: Documentation: 13: 52.7. Message Formats

JDBC error: Unexpected packet type: 25

2021-06-09 Thread Ignacio Rey
Hello, I'm sometimes getting this error from the PostgreSQL JDBC driver (version 42.2.10): java.io.IOException: Unexpected packet type: 25 (Full stack trace at the end of this message). Looks a lot like a bug or a version mismatch. The latter is unlikely since the driver is relative