
Brian Clark
Member of Product Staff at Databricks, leading Lakebase; previously VP of Product at Neon (acquired by Databricks)
1
APPEARANCES
1
PODCASTS
012
DEC 30
JAN 6
JAN 13
JAN 20
JAN 27
FEB 3
FEB 10
FEB 17
FEB 24
MAR 3
MAR 10
MAR 17
MAR 24
MAR 31
APR 7
APR 14
APR 21
APR 28
MAY 5
MAY 12
MAY 19
MAY 26
JUN 2
JUN 9
JUN 16
JUN 23
JUN 30
JUL 7
JUL 14
JUL 21
JUL 28
AUG 4
AUG 11
AUG 18
AUG 25
SEP 1
SEP 8
SEP 15
SEP 22
SEP 29
OCT 6
OCT 13
OCT 20
OCT 27
NOV 3
NOV 10
NOV 17
NOV 24
DEC 1
DEC 8
DEC 15
DEC 22
DEC 29
JAN 5
JAN 12
JAN 19
JAN 26
FEB 2
FEB 9
FEB 16
FEB 23
MAR 2
MAR 9
MAR 16
MAR 23
MAR 30
APR 6
APR 13
APR 20
APR 27
MAY 4
MAY 11
MAY 18
MAY 25
JUN 1
JUN 8
JUN 15
JUN 22
JUN 29
JUL 6
JUL 13
JUL 20
JUL 27
AUG 3
AUG 10
AUG 17
AUG 24
AUG 31
SEP 7
SEP 14
SEP 21
Jun 9, 2026
Creating checkpoints by gaslighting a Postgres database
5:34
6:01
R
5:28Ryan DonovanHOST
Is there any downside besides the token spend to letting the AI spinning it up?

Brian ClarkGUEST
I think, like, the AI can spin it up and just like spinning it down, uh, you know, agents, um, are gonna hit the command, like the API call to spin something up, and then wait for the response, uh, and know that then they can start using it, and that's the same thing on the, uh, on the destruction of these things, right? When they, uh, they have to go say, "Hey, destroy this database," and then wait around for the, like, the compute to shut down and then delete the branches afterwards.

Brian ClarkGUEST
Uh, and that's the thing, if you're doing a fan-out strategy of 10 different agents-Your goal is not to basically save money at this point.
18 MINS LATER