pgjdbc/pgjdbc GitHub issues and pull requests (mirror)  
help / color / mirror / Atom feed
[pgjdbc/pgjdbc] PR #3509: Add back application name setting
34+ messages / 2 participants
[nested] [flat]

* [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-04 22:47  "joejensen (@joejensen)" <[email protected]>
  0 siblings, 0 replies; 34+ messages in thread

From: joejensen (@joejensen) @ 2025-02-04 22:47 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

Fixes #3508, by adding back the application_name startup parameters during the initial connection.

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-04 22:51  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-02-04 22:51 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

this https://github.com/pgjdbc/pgjdbc/pull/3491 doesn't fix it ?

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-04 22:59  "joejensen (@joejensen)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: joejensen (@joejensen) @ 2025-02-04 22:59 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

> this #3491 doesn't fix it ?

No, on line #906 it's actually returning immediately if the version >= 9.0 so it never reaches that code.  Also, the postgres logging doen't include the application name in the initial connection logs if it is not included at startup.

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-04 23:02  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-02-04 23:02 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

The problem is we really don't know the server version here. We don't know if we are on version 9 or not at this point

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-04 23:09  "joejensen (@joejensen)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: joejensen (@joejensen) @ 2025-02-04 23:09 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

Maybe I'm missing something but isn't the purpose of the minServerVersion, so that we can infer what we expect the minimum version to be?

I'd be happy to add another way(property) of indicating this should happen but it seems redundant.  Not having this occur at startup causes a regression from the last several driver versions for my use case.

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-04 23:24  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-02-04 23:24 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

I'd like to see the regression. 
FYI, there is no information in the startup telling use the version, we have to wait until we are connected to find out which is why it is moved later in the code

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-04 23:41  "joejensen (@joejensen)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: joejensen (@joejensen) @ 2025-02-04 23:41 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

The regression is for the issue described on #2111, I can provide more up to date log examples if needed.  

Essentially the initial application logging in the postgresql logs do not include the application name unless it is set in the startup request.

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-04 23:44  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-02-04 23:44 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

As I said the problem is we do not know the version number of the server until after the startup packet.

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-05 00:12  "joejensen (@joejensen)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: joejensen (@joejensen) @ 2025-02-05 00:12 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

I really would like to understand what I am misunderstanding.  Anticipating what the server version will be before connecting seems to be the entire purpose of the assumeMinServerVersion property.  If we remove this use case it does not appear to be used anywhere else.


^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-05 00:14  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-02-05 00:14 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

In order to do that you would have to set that property. Are you doing that now ?

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-05 00:15  "joejensen (@joejensen)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: joejensen (@joejensen) @ 2025-02-05 00:15 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

yes

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-05 00:17  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-02-05 00:17 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

In which case we would have to remove the setting of it later if it gets set here

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-05 00:23  "joejensen (@joejensen)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: joejensen (@joejensen) @ 2025-02-05 00:23 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

It isn't getting called later already  Nothing in runInitialQueries is occurring if you set a minimum server version >= 9.0

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-05 00:24  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-02-05 00:24 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

My point is that I don't want it set 2x

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-05 00:25  "joejensen (@joejensen)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: joejensen (@joejensen) @ 2025-02-05 00:25 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

definitely agree with that.

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-05 00:25  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-02-05 00:25 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

we set application name in runInitialQueries

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-05 00:31  "joejensen (@joejensen)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: joejensen (@joejensen) @ 2025-02-05 00:31 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

But run initial queries is not getting executed if the assumeMinServerVersion is set to a value >= 9.0.  

https://github.com/pgjdbc/pgjdbc/blob/master/pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionF...

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-05 00:42  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-02-05 00:42 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

Well that's just wrong. The other things need to be set as well.

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-05 00:46  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-02-05 00:46 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

Interesting as someone is setting APPLICATION_NAME
```
16385 | test    | 10879 |            |    16384 | test    | PostgreSQL JDBC Driver | 127.0.0.1   |                 |       52308 | 2025-02-04 19:43:53.65606-05  |                               | 2025-02-04 19:44:03.301573-05 | 2025-02-04 19:44:03.301968-05 | Client          | ClientRead          | idle   |             |              |          | SELECT c.oid, a.attnum, a.attname, c.relname, n.nspname, a.attnotnull OR (t.typtype = 'd' AND t.typnotnull), a.attidentity != '' OR pg_catalog.pg_get_expr(d.adbin, d.adrelid) LIKE '%nextval(%' FROM pg_catalog.pg_class c JOIN pg_catalog.pg_namespace n ON (c.relnamespace = n.oid) JOIN pg_catalog.pg_attribute a ON (c.oid = a.attrelid) JOIN pg_catalog.pg_type t ON (a.atttypid = t.oid) LEFT JOIN pg_catalog.pg_attrdef d ON (d.adrelid = a.attrelid AND d.adnum = a.attnum) JOIN (SELECT 16386 AS oid , 1 AS attnum UNION ALL SELECT 16386, 2 UNION ALL SELECT 16386, 3) vals ON (c.oid = vals.oid AND a.attnum = vals.attnum) where c.oid in (16386) | client backend
```

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-05 00:54  "joejensen (@joejensen)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: joejensen (@joejensen) @ 2025-02-05 00:54 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

I don't know your connection string, for me it works unless I set the assumeMinServerVersion connection property to 9.0 or greater, if I omit that property the name gets set, just too late for the initial connection logging.

It does appear that you could still skip the initial queries if the assume version was >= 12.  Everything else would already be set correctly.

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-05 01:00  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-02-05 01:00 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

OK, I need to look at this some more. It would be useful to write tests for this.

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-05 01:01  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-02-05 01:01 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

> I don't know your connection string, for me it works unless I set the assumeMinServerVersion connection property to 9.0 or greater, if I omit that property the name gets set, just too late for the initial connection logging.
> 
> It does appear that you could still skip the initial queries if the assume version was >= 12. Everything else would already be set correctly.

Why do you need this at initial connection logging ?


^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-05 03:29  "joejensen (@joejensen)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: joejensen (@joejensen) @ 2025-02-05 03:29 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

I have log monitoring tools that track which applications are connecting and when.  It might be possible to parse this out of subsequent statements but it wouldn't be simple.  I know some common tools, like pgBadger, do the same thing.  Without this being set at startup all new connections report as "unknown".

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-05 10:44  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-02-05 10:44 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java)

Got it, thanks!

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-06 22:32  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-02-06 22:32 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

OK, I think we need to add it back. I think the runInitialQueries needs to be tightened up and we need to document this better.
`runInitialQueries should still set `extra_float_digits=3` for versions 9-12 and  `extra_float_digits=2` for versions less than 9

Thanks!

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-18 22:27  "joejensen (@joejensen)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: joejensen (@joejensen) @ 2025-02-18 22:27 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

I believe the latest changes will run the initial queries only when necessary. 
On PG 12 and later no initial queries are required assuming the assumMinServerVersion is set correctly.
On PG 9-11.x only the extra digits query is required if assumeMinServerVersion is set correctly.

I was able to add a unit test that fails for the original code, when assumeMinServerVersion was set to >= 9.0 resulting in the application name being blank.  However, I don't see a straight-forward way to verify that it's being set in the startup parameters rather than via the initial queries (in the test harness at least).  If you have any ideas, I would appreciate it.

I also added a note about this use-case into the documentation, not sure if it belongs anywhere else.


^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-19 15:20  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-02-19 15:20 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java:926)

what happens here if assumeVersion.getVersionNum() returns `null` ?

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-19 16:21  "joejensen (@joejensen)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: joejensen (@joejensen) @ 2025-02-19 16:21 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java:926)

It can't.  ServerVersion.from(String) converts a null assumeMinServerVersion to a 0, which is what is returned if no min server version was provided.

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-19 23:32  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-02-19 23:32 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java:926)

Can you just confirm by adding a test without the `PGProperty.ASSUME_MIN_SERVER_VERSION.getOrDefault(info)` set ?

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-02-28 19:55  "joejensen (@joejensen)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: joejensen (@joejensen) @ 2025-02-28 19:55 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java:926)

I can but that scenario is already tested by ParameterStatusTest.expectedInitialParameters.

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-03-17 15:36  "joejensen (@joejensen)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: joejensen (@joejensen) @ 2025-03-17 15:36 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java:926)

Do we want to add additional test for this same scenario?

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-04-02 16:15  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-04-02 16:15 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java:926)

when in doubt add tests

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-04-15 17:45  "joejensen (@joejensen)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: joejensen (@joejensen) @ 2025-04-15 17:45 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java:926)

Added the additional test and rebased over master.

^ permalink  raw  reply  [nested|flat] 34+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
@ 2025-04-28 22:37  "davecramer (@davecramer)" <[email protected]>
  32 siblings, 0 replies; 34+ messages in thread

From: davecramer (@davecramer) @ 2025-04-28 22:37 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java:923)

I wouldn't mind seeing some more explanation as to how we used the following tests to come to that conclusion.

^ permalink  raw  reply  [nested|flat] 34+ messages in thread


end of thread, other threads:[~2025-04-28 22:37 UTC | newest]

Thread overview: 34+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-02-04 22:47 [pgjdbc/pgjdbc] PR #3509: Add back application name setting "joejensen (@joejensen)" <[email protected]>
2025-02-04 22:51 ` "davecramer (@davecramer)" <[email protected]>
2025-02-04 22:59 ` "joejensen (@joejensen)" <[email protected]>
2025-02-04 23:02 ` "davecramer (@davecramer)" <[email protected]>
2025-02-04 23:09 ` "joejensen (@joejensen)" <[email protected]>
2025-02-04 23:24 ` "davecramer (@davecramer)" <[email protected]>
2025-02-04 23:41 ` "joejensen (@joejensen)" <[email protected]>
2025-02-04 23:44 ` "davecramer (@davecramer)" <[email protected]>
2025-02-05 00:12 ` "joejensen (@joejensen)" <[email protected]>
2025-02-05 00:14 ` "davecramer (@davecramer)" <[email protected]>
2025-02-05 00:15 ` "joejensen (@joejensen)" <[email protected]>
2025-02-05 00:17 ` "davecramer (@davecramer)" <[email protected]>
2025-02-05 00:23 ` "joejensen (@joejensen)" <[email protected]>
2025-02-05 00:24 ` "davecramer (@davecramer)" <[email protected]>
2025-02-05 00:25 ` "joejensen (@joejensen)" <[email protected]>
2025-02-05 00:25 ` "davecramer (@davecramer)" <[email protected]>
2025-02-05 00:31 ` "joejensen (@joejensen)" <[email protected]>
2025-02-05 00:42 ` "davecramer (@davecramer)" <[email protected]>
2025-02-05 00:46 ` "davecramer (@davecramer)" <[email protected]>
2025-02-05 00:54 ` "joejensen (@joejensen)" <[email protected]>
2025-02-05 01:00 ` "davecramer (@davecramer)" <[email protected]>
2025-02-05 01:01 ` "davecramer (@davecramer)" <[email protected]>
2025-02-05 03:29 ` "joejensen (@joejensen)" <[email protected]>
2025-02-05 10:44 ` "davecramer (@davecramer)" <[email protected]>
2025-02-06 22:32 ` "davecramer (@davecramer)" <[email protected]>
2025-02-18 22:27 ` "joejensen (@joejensen)" <[email protected]>
2025-02-19 15:20 ` "davecramer (@davecramer)" <[email protected]>
2025-02-19 16:21 ` "joejensen (@joejensen)" <[email protected]>
2025-02-19 23:32 ` "davecramer (@davecramer)" <[email protected]>
2025-02-28 19:55 ` "joejensen (@joejensen)" <[email protected]>
2025-03-17 15:36 ` "joejensen (@joejensen)" <[email protected]>
2025-04-02 16:15 ` "davecramer (@davecramer)" <[email protected]>
2025-04-15 17:45 ` "joejensen (@joejensen)" <[email protected]>
2025-04-28 22:37 ` "davecramer (@davecramer)" <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox