I have a Postgres instance running on an Azure VM, which is inside an Azure Virtual Network, and the VM has a hostname. Connecting with PostgreSQL using the IP address works, but when I try to connect using the hostname it gives this error:
psql: server closed the connection unexpectedly
...
My azure VM is inside a vnet and has the hostname X.postgres.database.com. I tried to have a connection with the postgres which is running inside the VM using the hostname but it fails. Trying to connect with the IP address works.
And I also can ping to the VM using the hostname, since I have and...
My azure VM is inside a vnet and has the hostname X.postgres.database.com. I tried to have a connection with the postgres which is running inside the VM using the hostname but it fails. Trying to connect with the IP address works.
And I also can ping to the VM using the hostname, since I have and...
just a general FYI folks; while this isn't a particularly big problem on our site, referring to it as a "forum" gives folks the wrong idea about how we operate. Refer to dba.se as as "community" instead of a "forum".
I was under the impression that Stack Exchange sites were forums, or forum-like objects.
If they are not forums: Why aren't they? What defines a forum?
Today is going to be a timezone data analysis extravaganza.
I have times in different time zones attached to the same entity, and going to need to figure out which time zone to choose as the one for reporting the entity. Plus some stuff is time of day compared across facilities where the timezone needs to be discarded (but they'll need to be conformed to some chosen timezone first). Can't win.
@PaulWhite That crossed my mind (briefly) but I thought it was sort of covered by "if you're doing a lot of inserts here, this is a bad idea." I wasn't really thinking about concurrency with unrelated reads though.
There are really a lot of issues with putting a scalar function in a constraint.
@PaulWhite They just accepted @HannahVernon's answer!
I was contemplating constructing an INSTEAD OF trigger. But, why.
Thank you, that is interesting. I wasn't even aware of the existence of sequences in SQL Server. Gaps are not an issue for me and I do not intend to insert the values manually so I should be safe about the error you warned about. — Pawel4 mins ago
Reading that question and I'm getting PTSD from having to use a scalar function to do XML processing because XML functions are not allowed in persisted computed columns...
There might be a separate reason I didn't use it here. It's not in our actual product in any case. It's in the test harness database's tables. Lots of XML expecteds and actuals and needing to extract things like whether the expected and actual hashes match and then if there is a collision, checking that the XML does actually fully match.
And that status is in a persisted column, I think.
> The requirement is that by default newest tasks gets the lowest priority (highest int value). After the task is in table it then can be prioritised/deprioritised for example priority value swapped with any other task in the table.
(the pacific northwest of the US is under a heat shield and apparently it extends into part of CA. Prior to the past 3 days, Seattle had recorded 3 total days of 105 degrees over the past hundred years and they have equaled that in consecutive days)
@billinkc yes, thanks. It's actually beautiful here today. The further west you go from here the hotter it gets until you hit the ocean, apparently. We're expecting it to get hotter over the next week or so, but for now it's super enjoyable here. Right now it's 26°C (79°F). There is a nice little breeze and it's only about 50% humidity.
@billinkc how's the Chicken Frying Capital of the Free World?